[warp-agent-staging]

Problem

Two triage runs (01a0a659-c48c and 01a0a658-27d1) used the triage-issue-local and dedupe-issue-local skills in warpdotdev/warp, whose prerequisite told the agent to install a parent skill from warpdotdev/oz-for-oss, a repository outside the triage agent's working environment, so the step could never actually be completed.

Solution

Rewrote the prerequisite in both skill files: read the parent skill when it is actually resolvable in the working environment, but when its declared source repo is not part of that environment, proceed directly with the local skill's own guidance instead of fetching or installing from an inaccessible repo.

Evidence

Source run 01a0a659-c48c: the agent invoked triage-issue-local while its required parent skill was absent, chose not to install or surface that prerequisite, and proceeded to apply the specialized guidance anyway. Source run 01a0a658-27d1: it invoked triage-issue-local and dedupe-issue-local without satisfying their prerequisite to verify or install the parent skills, since both parent files were absent from the checkout.

Expected effect

Future triage runs that trigger these two skills should stop silently skipping (or stalling on) an unreachable prerequisite, and instead consistently apply the repo-specific guidance using their own role's output contract.

Deferred/Rejected

3 findings deferred

Research-skill delegation misses: instruction already correct, tried in ~12 prior PRs; model variance. Per-step narration: covered by open PRs 918, 717. Do-not-seek-shipped-implementation: benchmark-specific, not a standing rule.

Regressions addressed

Source runs scored Sep 22, 2026 UTC.

• Run 01a0a659-c48c-7ae5-9cbd-69ea52b918b3 — Procedure Compliance: noncompliant
• Run 01a0a658-27d1-7706-aa9b-9c3d2d699760 — Procedure Compliance: noncompliant

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.