Context
Steering-section extension of the AI Hero course vetting effort — contract in docs/topics/pocock-course-lanes/PLAN.md (branch claude/plan-mode-discussion-55kszx); lanes 1–6 are #2899–#2904; sibling steering lane is #2909. Owns the third gap from the 2026-08-17 writing-for-agents re-evaluation: invocation-choice doctrine is absent, and our de facto posture is the opposite of upstream's default, with neither ever argued.
Fleet reality (measured 2026-08-17): 211 top-level skills — 137 disable-model-invocation: false, 17 missing the key entirely, 57 true (almost entirely the setup skills plus a few maintainer-only skills). The setup convention is enforced by convention, documented nowhere. The skill-quality:check listing-budget instrument measures the aggregate description cost, but no decision rubric exists for choosing a skill's invocation mode. Upstream's SKILL-MECHANICS.md default is the inverse: user-invoked unless the agent must reach the skill autonomously or another skill needs it. The router-skill pattern was rejected only as the ask-matt port ("marketplace shape differs") — never evaluated as a pattern for our 57+ user-invoked skills.
Session decision (user-confirmed 2026-08-17): evidence-driven rubric. Neither upstream's user-invoked default nor our model-invoked default is assumed correct. The rubric weighs: autonomous-reach need, cross-skill reach (invocation-reach invariant), real trigger-hit evidence, listing-budget data, cognitive load on the human, and surface coverage.
Evidence that must feed the rubric:
Scope constraint: ADR 0005 (bound instruction-surface work by question, not population). Shape as rubric-first + question-bounded application, not an unbounded 211-skill sweep. Reconcile with docs/topics/context-engineering-claude-5/ prior art (its design/skill-inventory.md population-derivation traps and the discipline:sweep-all router precedent).
Proposed work
- Open with
/planning:interview me per contract; lane discusses and decides — implementation leaves as filed work items
- Write the invocation-mode decision rubric and pick its one home (PLUGIN-PHILOSOPHY component stances, a convention-registry owner doc, or
playbooks:skill-authoring — decide, don't duplicate)
- Document the existing
setup-skill convention (currently undocumented)
- Decide the 17 skills missing the
disable-model-invocation key (explicit value or documented default)
- Evaluate the router-skill pattern on its merits (cognitive-load relief for user-invoked skills;
claude-ops:inventory and docs/SKILL-CHEAT-SHEET.md as existing partial answers)
- Apply the rubric question-bounded (e.g. per plugin or per workflow stage), using
skill-quality:check listing-budget before/after as the measurement
- Verify and disposition the invocation-reach invariant tracked strand
Acceptance criteria
References
Metadata
| Field |
Value |
| Category |
unspecified |
| Area |
skill-quality, docs (philosophy, conventions), all plugins (fleet) |
| Ecosystem |
unspecified |
Context
Steering-section extension of the AI Hero course vetting effort — contract in
docs/topics/pocock-course-lanes/PLAN.md(branchclaude/plan-mode-discussion-55kszx); lanes 1–6 are #2899–#2904; sibling steering lane is #2909. Owns the third gap from the 2026-08-17writing-for-agentsre-evaluation: invocation-choice doctrine is absent, and our de facto posture is the opposite of upstream's default, with neither ever argued.Fleet reality (measured 2026-08-17): 211 top-level skills — 137
disable-model-invocation: false, 17 missing the key entirely, 57true(almost entirely thesetupskills plus a few maintainer-only skills). The setup convention is enforced by convention, documented nowhere. Theskill-quality:check listing-budgetinstrument measures the aggregate description cost, but no decision rubric exists for choosing a skill's invocation mode. Upstream'sSKILL-MECHANICS.mddefault is the inverse: user-invoked unless the agent must reach the skill autonomously or another skill needs it. The router-skill pattern was rejected only as theask-mattport ("marketplace shape differs") — never evaluated as a pattern for our 57+ user-invoked skills.Session decision (user-confirmed 2026-08-17): evidence-driven rubric. Neither upstream's user-invoked default nor our model-invoked default is assumed correct. The rubric weighs: autonomous-reach need, cross-skill reach (invocation-reach invariant), real trigger-hit evidence, listing-budget data, cognitive load on the human, and surface coverage.
Evidence that must feed the rubric:
~/.claudeuser scope, so user-level personal skills don't travel — project/marketplace skills are the only steering that reaches cloud sessions (user-raised, steering-section session)disable-model-invocation: trueskill is unreachable from any other skill; substance landed unreleased upstream via PRs feat(planning): route incumbency-driven plan-review findings to incumbent mode #878/feat(typos-format): per-file typos autofix hook plugin #880 (.agents/invocation.md). Verify against current official Claude Code docs and record the dispositionScope constraint: ADR 0005 (bound instruction-surface work by question, not population). Shape as rubric-first + question-bounded application, not an unbounded 211-skill sweep. Reconcile with
docs/topics/context-engineering-claude-5/prior art (itsdesign/skill-inventory.mdpopulation-derivation traps and thediscipline:sweep-allrouter precedent).Proposed work
/planning:interview meper contract; lane discusses and decides — implementation leaves as filed work itemsplaybooks:skill-authoring— decide, don't duplicate)setup-skill convention (currently undocumented)disable-model-invocationkey (explicit value or documented default)claude-ops:inventoryanddocs/SKILL-CHEAT-SHEET.mdas existing partial answers)skill-quality:check listing-budgetbefore/after as the measurementAcceptance criteria
docs/upstream/aihero-course.mdfor lessons 3 (What Are Agent Skills), 4 (Write A Skill — invocation half), 5 (User Vs Project Skills, incl. the cloud-scope caveat)References
docs/upstream/mattpocock-skills.md— decomposition table + tracked strandsSKILL-MECHANICS.md(Invocation / Splitting by invocation / Router skills) and.agents/invocation.md(PRs feat(planning): route incumbency-driven plan-review findings to incumbent mode #878/feat(typos-format): per-file typos autofix hook plugin #880, unreleased)docs/adr/0005-bound-instruction-surface-work-by-question-not-population.mddocs/topics/context-engineering-claude-5/design/skill-inventory.mdMetadata