Stop skills from calling other user-invoked skills
Stop skills from calling other user-invoked skills Five skills (to-spec, wayfinder, to-tickets, triage, code-review) told the agent to call the Skill tool on setup-matt-pocock-skills as a missing-config precondition. It's user-invoked, so per .agents/invocation.md no other skill — user- or model-invoked — can ever reach it that way. PR #878 turned the old soft "/skill"-style prose into a literal "Call the Skill tool with ..." instruction without checking invocation type, which made this fire more reliably in the wrong direction. Reworded all five as instructions to tell the human to run it instead. diagnosing-bugs had the same problem handing its post-mortem off to improve-codebase-architecture, with no human anywhere in that loop to catch the failed call. Removed the hand-off outright rather than softening it, since it rarely fired in practice; Phase 6 is now "Cleanup" only. Added a carve-out to .agents/invocation.md's "Dependencies between them" section — the section PR #878 intro
What happened
The commit implemented changes to stop certain skills from invoking user-invoked skills, aligning with the .agents/invocation.md guidelines that prohibit such calls. Adjustments were made to both the language used in the skills and their interactions to prevent erroneous invocations.
Why it matters
This update enhances the development experience by preventing unintended interactions between skills, thereby ensuring users perform actions manually. It helps maintain the integrity of skill operations and reduces failure points in workflows, leading to more reliable automation.