Re-audited this while grilling a related question. The original report undercounted the instances, and it's gotten worse since filing.

Full instance list, as of today:

to-spec, wayfinder, to-tickets, triage, code-review — all five carried a missing-config precondition instructing the agent to call setup-matt-pocock-skills (user-invoked). The report named to-prd/to-issues/code-review/triage (old skill names for to-spec/to-tickets) but missed wayfinder.
diagnosing-bugs — a separate instance not in the original report: its Phase 6 post-mortem hands off to improve-codebase-architecture (also user-invoked), which is worse than the other five since diagnosing-bugs is model-invoked and often runs unattended — no human anywhere in that chain to catch the failed call.

It also got worse today. #878 (merged a few hours ago) did a repo-wide phrasing standardization — bare /skill-style prose → explicit Call the Skill tool with "name" — aimed at a real, separate problem (grill-with-docs → grilling not reliably firing). That audit checked whether a reference was operative vs. router prose, but never checked invocation type, so it mechanically rewrote all six of these into more-literal, more-likely-to-fire Skill tool calls against user-invoked targets. Made the bug this issue describes fire more often, not less.

Fix, including a carve-out in .agents/invocation.md so this doesn't happen a third time: #880

setup-matt-pocock-skills is being invoked by other skills #453

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions