Subagent-configuration audit methodology preloaded by the subagent-auditor agent. Dispatch subagent-auditor to audit subagent configuration files; the main conversation reaches this audit only through that agent.

2026-07-080

create-subagents

outcomeeng/foundation

ALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.

2026-07-080

agent-prompt-standards

outcomeeng/foundation

Agent prompt writing conventions enforced across all creator and auditor skills. Loaded by other skills, not invoked directly.

2026-07-050

audit-skills

outcomeeng/foundation

SKILL.md audit methodology preloaded by the skill-auditor agent. Dispatch skill-auditor to audit SKILL.md files; the main conversation reaches this audit only through that agent.

2026-07-050

create-skills

outcomeeng/foundation

ALWAYS invoke this skill when creating, editing, or improving SKILL.md files.

2026-07-050

design-frontend

outcomeeng/foundation

ALWAYS invoke this skill when designing or building web components, pages, or dashboards. NEVER design or build web UI without this skill.

2026-07-050

Ejecuta cualquier Skill con un clic

name	skill-standards
user-invocable	false
description	Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.
allowed-tools	Read

The canonical standards for skill authoring — frontmatter, XML structure, naming, descriptions, progressive disclosure, skill types, reference patterns, code-fence and bash constraints, validation, and script testing.

<success_criteria> Skills conform to these standards when, at minimum: (a) the SKILL.md is under 500 lines, (b) the body uses pure XML structure with no markdown headings, (c) <objective> and <success_criteria> tags are present, (d) the description matches the invocation path — directive when Claude auto-activates the skill by description-match, passive when it is invoked only by exact name or by a parent skill (a user-invocable: false reference, or a user-invocable protocol/loop skill a timer targets), and (e) the skill passes /audit-skills with no must-fix items. </success_criteria>

<reference_note> This is a reference skill. /create-skills and /audit-skills load these standards automatically. Do not invoke directly. </reference_note>

<repo_local_overlay> When another skill loads this reference inside a repository, check for spx/local/skills.md at the repository root. Read that file after this reference if it exists and apply it as the repo-local specialization (e.g., marketplace-specific naming conventions or additional constraints). A local overlay supplements skill behavior; it does not declare product truth. </repo_local_overlay>

<skill_organization>

Skills follow a reference pattern to avoid duplication:

Foundational skill (e.g., /test) — core principles and domain-agnostic patterns.
Language-specific skills (e.g., /test-python, /test-typescript) — reference the foundational skill, provide only language-specific implementations.
Reference skills (e.g., /typescript-standards, /skill-standards) — standards loaded by other skills, never invoked directly.

For language-specific skills that reference a foundation, use unqualified names (/test) so they resolve to whichever foundational skill is installed.

Skill invocation limitations: Skills cannot automatically invoke other skills. They can:

Instruct Claude to read another skill file first
Reference foundational concepts by skill name
Be invoked sequentially by the user or Claude

</skill_organization>

Every SKILL.md starts with YAML frontmatter. The canonical catalog of supported fields lives in the Claude Code docs at https://code.claude.com/docs/en/skills#frontmatter-reference. Read the docs page when a question is about execution behavior; read this section when it is about how this marketplace authors skills.

Field	Required	Constraint
`name`	No	Lowercase letters, numbers, hyphens. ≤64 chars. Must match the directory name when set. If omitted, the directory name is used.
`description`	Recommended	Directive style for invoked skills (see `<descriptions>`); passive for references. Combined with `when_to_use` the listing is capped at 1,536 chars; put the key trigger first.
`when_to_use`	No	Extra trigger phrases or example requests appended to `description` in the skill listing. Shares the 1,536-char cap.
`argument-hint`	No	Free-text hint shown during `/` autocomplete (e.g. `[issue-number]`).
`arguments`	No	Named positional arguments for `$name` substitution in the body. Space-separated string or YAML list; names map to argument positions in order.
`allowed-tools`	No	Tools Claude may use without per-call approval while the skill is active. Space-separated string or YAML list. Restrict for audit (read-only) and reference skills.
`disable-model-invocation`	No	`true` to block programmatic invocation entirely — Claude cannot load the skill, including via the Skill tool, and the skill cannot be preloaded into subagents. Use for `/deploy`-style user-only commands. Default `false`.
`user-invocable`	No	`false` to hide from the `/` autocomplete menu while keeping Claude able to invoke via the Skill tool. Description stays in context. Use for reference skills that other skills load programmatically. Default `true`.
`model`	No	Model override for this skill (`opus`, `sonnet`, `haiku`, or `inherit`). Marketplace verification-sensitive surfaces use explicit `sonnet` and never use session inheritance.
`effort`	No	Effort level (`low`, `medium`, `high`, `xhigh`, `max`) — overrides the session effort while the skill is active.
`context`	No	`fork` to run the skill in a forked subagent context. Combine with `agent`.
`agent`	No	Subagent type to use when `context: fork` is set (`Explore`, `Plan`, `general-purpose`, or a custom agent). Defaults to `general-purpose`.
`hooks`	No	Hooks scoped to this skill's lifecycle. See the Claude Code hooks reference for shape.
`paths`	No	Glob patterns that limit auto-activation to matching files. Comma-separated string or YAML list.
`shell`	No	`bash` (default) or `powershell` for the skill's inline and fenced command-injection blocks. The `powershell` value requires `CLAUDE_CODE_USE_POWERSHELL_TOOL=1`.

Visibility vs invocability. Two fields gate how a skill is reached. They are not aliases — pick deliberately. Automation re-entry — a scheduled wakeup, heartbeat, or /loop — arrives as a user-style prompt because the harness offers no Claude-private heartbeat, so it follows the User /skill column exactly:

Frontmatter	User `/skill`	Claude (Skill tool)	Subagent preload	Automation re-entry	Description in context
(default)	Yes	Yes	Yes	Yes	Always
`disable-model-invocation: true`	Yes	No	No	Yes	Not in context
`user-invocable: false`	No	Yes	Yes	No	Always

Pick the gate by role:

A reference skill another SKILL.md loads via the Skill tool, or a background-knowledge skill, uses user-invocable: false — hidden from the / menu, still loadable by Claude and preloadable into subagents.
A user-only side-effecting command (/deploy) uses disable-model-invocation: true. NEVER set it on a skill other skills or subagents must load: it blocks the Skill-tool call (surfacing Skill <name> cannot be used with Skill tool due to disable-model-invocation) AND blocks subagent preloading.
A skill any automation loop re-enters — a scheduled wakeup, heartbeat, or /loop target — MUST be user-invocable (leave the default; never user-invocable: false). Automation fires as a user-style prompt, so user-invocable: false rejects it and no Claude-private heartbeat exists to bypass that. When a loop body is otherwise reference-like, expose a user-invocable entry the loop targets rather than gating the body. Such a loop body keeps a passive description — it is invoked by exact name (the timer or a parent skill), not by description-match, so a directive description would only cause false auto-activations. A user-invocable skill with a passive description is the correct shape here, not a defect.

# Invoked skill (routing, workflow, creation)
---
name: create-skills
description: >-
  ALWAYS invoke this skill when creating, editing, or improving SKILL.md files.
  NEVER create or modify skills without this skill.
---

# Reference skill (standards, loaded programmatically by other skills)
---
name: skill-standards
user-invocable: false
description: >-
  Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.
allowed-tools: Read
---

# User-only command (side effects; Claude must not auto-trigger)
---
name: deploy
disable-model-invocation: true
description: Deploy the application to production
allowed-tools: Bash(git *) Bash(./deploy *)
---

Audit skills (audit-*) must add allowed-tools: Read, Grep, Glob, Bash per the read-only rule for audit skills — audit runs never modify files.

Directory match is mandatory. skills/author/ → name: author. A mismatch breaks skill lookup.

Field skills: is NOT supported on SKILL.md. It exists only on subagent definitions (agents/*.md), where it preloads skill content as reference material into the subagent's startup context. The official docs page above lists every field a SKILL.md actually accepts; skills: is not among them. To make a reference skill available to another skill, set user-invocable: false on the reference and have the parent skill invoke it via the Skill tool — there is no preload field on the consumer side.

Command-capability fields. A SKILL.md carries every capability a slash command had — argument-hint/arguments, allowed-tools restriction, plus !-dynamic context and @ file references in the body. The authoring and audit rules for that surface live in ${CLAUDE_SKILL_DIR}/references/command-capabilities.md; read it before authoring a skill that takes arguments, injects state, or restricts tools.

<naming_conventions>

The name field is the user invocation path (/skill-name). Match user speech patterns.

Rules:

Use domain acronyms: author not author-spec-tree-artifacts
Use terms users actually say: test-python not python-unit-test-framework
Think "CD-ROM" not "Compact Disc Read Only Memory"
Directory name MUST match: skills/author/ → name: author

Naming form: invoked workflow skills use imperative verbs. Reference skills use noun phrases ending in the domain they standardize, such as skill-standards or typescript-test-standards.

Vocabulary precedence: Skill-name grammar does not override declared methodology vocabulary. When a term can belong both to a skill-name form and to another taxonomy, read the source that declares that taxonomy and inspect file history before calling the term a naming defect.

Treat generated runtime output and implementation names as lower-layer evidence, never as the authority for vocabulary classification.

Material-change rule: Any material change to a skill implies renaming all skills in the entire plugin to match the latest develop rules.

# ✅ Matches user speech
name: author # Users say "author a spec"
name: test-typescript # Users say "test TypeScript code"
name: bootstrap # Users say "bootstrap the spec tree"

# ❌ Nobody says these
name: author-spec-tree-artifacts # Too verbose
name: typescript-unit-framework # Wrong order

</naming_conventions>

The description field governs skill selection. Claude has a character budget for all skill metadata — when exceeded, skills become invisible.

Activation rates by style (Seleznov, 650 automated trials, Feb 2026):

Style	Activation	Pattern
Passive	~77%	`Use when…`
Expanded	~93%	`…or any X-related task`
Directive	~100%	`ALWAYS invoke… NEVER X without`

Use directive descriptions for invoked skills:

description: >-
  ALWAYS invoke this skill when <triggers>.

NEVER constraint — add only when it disambiguates. A NEVER line helps when:

The skill is the only one with that negative (e.g., NEVER work on the spec tree without loading context — only contextualizing says this).
Claude has a strong built-in alternative the negative prevents (e.g., NEVER run git commit without this skill — Claude would just run git commit directly).

Omit NEVER when multiple skills share the same negative (adds noise) or the ALWAYS trigger is already specific enough.

Language-after-artifact (matches user speech):

# ✅ "audit ADRs for Python"
ALWAYS invoke this skill when auditing ADRs for Python.

# ❌ "audit Python ADRs"
ALWAYS invoke this skill when auditing Python ADRs.

Match user speech over formal jargon: Use abbreviations users would use (ADR not Architecture Decision Record). Avoid corporate speak.

Reference skills use user-invocable: false with a passive description:

user-invocable: false
description: >-
  Python code standards enforced across all skills. Loaded by other skills, not invoked directly.

Protocol and loop-body skills that a parent skill loads, or that a timer fires by exact name (a heartbeat re-entry target), keep a passive description while staying user-invocable — they are never reached by description-match, so a directive description would only cause false auto-activations. See the gate-by-role rules in <frontmatter>.

Agent-preloaded audit skills — an audit-* skill a dedicated *-auditor agent preloads through its skills: field — keep a passive, dispatch-steering description and carry a <dispatch_gate> at the top of the body. The auditor agent's own directive description is the description-match entry point; a directive ALWAYS invoke this skill on the audit skill only pulls the main conversation into running the audit in its own context — the very bias the dispatched agent's isolated context exists to remove. The skill keeps its allowed-tools and stays user-invocable so the auditor agent can preload it; NEVER block the main conversation with disable-model-invocation, which also blocks that preload and skill-to-skill loading — the passive description plus the dispatch gate carry the rule instead.

description: >-
  Test-evidence audit methodology preloaded by the test-evidence-auditor agent.
  Dispatch test-evidence-auditor to audit test evidence; the main conversation
  reaches this audit only through that agent.

Conflict resolution: If Claude picks the wrong skill, descriptions are too similar. Make trigger terms distinct — "sales data in Excel" vs "log files and system metrics".

<xml_structure>

Skills use pure XML structure — no markdown headings (#, ##, ###) anywhere in the body. Keep markdown formatting within content (bold, italic, lists, tables, code blocks, links).

Why pure XML: unambiguous section boundaries, consistent cross-skill structure, better token efficiency, better Claude performance.

Required tags (every skill):

Tag	Content
`<objective>`	The observable output the skill produces, in a definite shape — one sentence, not an actor or an activity, not a summary of the skill. See `/agent-prompt-standards` `<objective_shape>`.
`<success_criteria>`	The properties that prove the output is sound — not a re-list of the workflow steps.

Router-pattern tags (skills that route to multiple workflows):

Tag	Content
`<essential_principles>`	Principles that apply regardless of which workflow runs. Inline.
`<intake>`	Question to ask the user to determine routing.
`<routing>`	Table mapping responses to workflow files.
`<reference_index>`	List of available reference files.
`<workflows_index>`	List of available workflow files.

Workflow-file tags (files inside workflows/):

Tag	Content
`<required_reading>`	Which reference files to load before running this workflow.
`<process>`	Step-by-step procedure.
`<success_criteria>`	When this workflow is complete.

Conditional tags (include when the skill's complexity or purpose calls for them):

Tag	When to include
`<quick_start>`	On-demand tool skills with a meaningful fast path. Omit for foundation, gate, validator, and reference skills — completeness is the point.
`<dispatch_gate>`	Agent-preloaded audit skills. A hard stop at the top of the body that halts a main-conversation invocation and directs it to dispatch the corresponding auditor agent. Omit for every other skill type.
`<context>`	Background needed before starting.
`<workflow>`	Sequential steps (non-router skills).
`<advanced_features>`	Progressive disclosure for deep-dive topics.
`<validation>`	Verification checks.
`<examples>`	Input/output pairs.
`<anti_patterns>`	Common mistakes to avoid.
`<security_checklist>`	Skills with security implications.
`<testing>`	Testing workflows or validation steps.
`<common_patterns>`	Reusable recipes.
`<reference_guides>`	Pointers to detailed reference files.
`<failure_modes>`	Named failures from actual usage — what happened, why, how to avoid.

This table is representative, not exhaustive: a skill may add semantically named domain sections beyond it (this file's <frontmatter>, <descriptions>, and reference-pointer sections such as <platform_constraints> and <script_standards> are examples).

Nesting: XML tags can nest for hierarchical content.

<examples>
  <example number="1">
    <input>User input</input>
    <output>Expected output</output>
  </example>
</examples>

Close every tag. Unclosed tags break parsing.

<context> bash blocks fire on every skill load. Every !command`` line inside <context> runs unconditionally each time the skill is invoked — including false-positive activations triggered by directive descriptions matching adjacent terms. Heavy commands (session lists, full file contents, cache enumerations) compound the per-load tax.

Constraints:

Filter expensive commands (spx session list --status doing,todo, git log -10, head -N) so output stays bounded.
Move data into the workflow file that actually consumes it when the skill loader doesn't need it for trigger evaluation. The <context> block is for trigger-time orientation, not workflow inputs.
Avoid commands whose output grows monotonically (archives, full caches, full file trees).

Semantic names: <workflow> not <steps>, <success_criteria> not <done>, <anti_patterns> not <dont_do>.

Reference tags in prose by name: "Using the schema in <schema> tags…", "Follow the workflow in <workflow>…". Makes structure self-documenting.

Intelligence rules — match structure to complexity:

Skill class	Expected tags
Simple (single domain)	`<objective>`, `<success_criteria>`, optionally `<quick_start>`
Medium (multiple patterns)	Required + `<workflow>` and/or `<examples>`
Complex (multi-domain, API, sec)	Required + router pattern + appropriate conditional tags
Foundation / gate / validator / reference	Required + `<workflow>`. Omit `<quick_start>` — no abbreviated path exists.
Auditor (agent-preloaded)	The canonical auditor skeleton — read `references/auditor-skeleton.md` when authoring or auditing an `audit-` skill. Omit* `<quick_start>`.

Don't over-engineer simple skills. Don't under-specify complex ones.

</xml_structure>

<progressive_disclosure>

SKILL.md is an overview. Reference files carry detail. Claude loads reference files only when needed.

Rules:

Keep SKILL.md under 500 lines.
References live in references/ one level deep from SKILL.md. Do not nest references that read other references — Claude may only partially read transitive files.
Reference files over 100 lines need a table of contents at the top, so partial reads still see the full scope.
Use forward slashes in every path — references/guide.md, never references\guide.md. Works across platforms.

Token efficiency: simple task loads SKILL.md only (~500 tokens); medium loads SKILL.md + one reference (~1000); complex loads SKILL.md + multiple (~2000+).

✅ One level deep
SKILL.md → references/advanced.md (complete info)
         → references/examples.md (complete info)

❌ Nested
SKILL.md → references/advanced.md → references/details.md → actual info

Name reference files descriptively — xml-structure-examples.md, not examples.md. The filename is also a table-of-contents entry in <reference_index>.

Every reference file must be cited. A file in references/ that is not mentioned by SKILL.md or any workflow file is orphaned — it costs ~1,800+ tokens per speculative read (Claude tends to open siblings of cited references) and signals either dead content or a missing cross-reference. Either delete the file or add an explicit <required_reading> from the workflow that needs it. Verify before committing: grep -rn "<filename>" <skill-dir>/.

</progressive_disclosure>

The context window is shared. A skill competes for tokens with the system prompt, conversation history, other skills' metadata, and the user's request.

Test every sentence: "Does removing this reduce Claude's effectiveness at the task?" If no — cut it.

What Claude already knows (never include):

General programming knowledge
Language syntax and standard-library APIs
Common design patterns
How to use its own tools

What Claude needs (include):

Product-specific conventions that contradict common patterns
Domain knowledge not in training data
Failure modes from actual usage (not hypotheticals)
Verification commands and thresholds

Concrete over abstract:

❌ "Ensure coverage is maintained"
✅ "Coverage delta must be ≤0.5%. Run: pnpm test --coverage | grep target.ts"

When to elaborate: the concept is domain-specific (not general programming), the pattern is non-obvious or counterintuitive, or context affects behavior in subtle ways.

<skill_types>

Six skill types. Each has a distinct purpose and primary output.

Type	Purpose	Primary output	Key sections
Builder	Create new artifacts	Code, documents, widgets, configs	Required clarifications, output spec, domain standards, templates in `assets/`
Guide	Teach procedures	Step-by-step workflows, tutorials	Numbered workflow, input→output example pairs, decision trees
Automation	Execute multi-step processes	Processed files, transformed data	Tested scripts in `scripts/`, error handling, dependencies, I/O contracts
Analyzer	Extract insights	Reports, summaries, reviews	Analysis scope, evaluation criteria, output format, synthesis
Validator	Enforce quality	Pass/fail verdicts, scores	Criteria with thresholds, scoring rubric, remediation guidance; `user-invocable: false` when invoked only by agents or explicit `Skill(name)` calls
Reference	Share domain knowledge	Standards loaded by other skills	`user-invocable: false`, passive description, `allowed-tools: Read`

Type-selection rule of thumb:

Creates new artifacts → Builder
Teaches how-to → Guide
Executes processes → Automation
Extracts insights → Analyzer
Checks quality → Validator
Shares knowledge multiple skills need → Reference

</skill_types>

<reference_skills>

Reference skills hold shared domain knowledge that multiple skills need. They are not invoked directly — consuming skills reach them via /skill-name references in their text.

When to create a reference skill. Two or more skills in the same plugin need the same domain knowledge (standards, patterns, anti-patterns, conventions). Alternatives fail: duplicating the content creates maintenance drift, and putting it in one skill's references/ directory makes it unreachable from the other skill's ${CLAUDE_SKILL_DIR}.

Required frontmatter:

---
name: {domain}-standards
user-invocable: false
description: >-
  {Domain} standards enforced across all skills. Loaded by other skills, not invoked directly.
allowed-tools: Read
---

user-invocable: false — prevents false activations from user prompts.
Passive description (no ALWAYS/NEVER) — directive descriptions trigger false activations for a reference.
allowed-tools: Read — reference skills only read.

How consuming skills reference it. Write the reference skill path in running text; Claude loads the reference into context on encounter.

# In test-typescript/SKILL.md:

See `/typescript-test-standards` for test file naming, execution levels, and reusable test patterns.

# In audit-typescript-tests/SKILL.md:

Before auditing, read `/typescript-test-standards` for the complete catalog of TypeScript test rules.

Naming convention: {domain}-standards for standards. Examples: typescript-test-standards, skill-standards, agent-prompt-standards.

Extraction completeness test. When factoring a standards reference out of a builder/auditor pair, the extraction is complete only when the corresponding audit skill loads the new reference and nothing else for standards. If the auditor still reads files from the builder's references/ directory for standards, content is still stranded there — finish the move. The same rule catches partial extractions: a standards file in a creator skill's references/ directory that the auditor needs is a bug, not an architecture.

Anti-patterns:

Directive descriptions (ALWAYS/NEVER) — cause false activations.
Shared content buried in one skill's references/ — ${CLAUDE_SKILL_DIR} is isolated per skill.
Same content duplicated across multiple references/ — drifts.
Partial extraction: naming a new standards skill while leaving the meat in the builder's references/ — the auditor keeps reading the old location and the rename becomes a lie.

</reference_skills>

<templates_and_variables>

Reference skill-bundled files with the Claude Code skill-directory token. The runtime variable scopes (${CLAUDE_SKILL_DIR}, ${CLAUDE_PLUGIN_ROOT}, ${CLAUDE_PLUGIN_DATA}, $CLAUDE_PROJECT_DIR), where each one resolves, and hook command: path examples live in ${CLAUDE_SKILL_DIR}/references/runtime-variables.md. Read it before referencing bundled files or wiring hook commands. Hook authoring patterns — the SessionStart + $CLAUDE_ENV_FILE session-identity mechanism and the plugin hooks/ directory layout — live in ${CLAUDE_SKILL_DIR}/references/plugin-hooks.md.

</templates_and_variables>

<platform_constraints>

Two platform footguns affect skill authoring: dprint's markup_fmt handling of nested code fences, and Claude Code's bash-safety checker for ! expansion. Read ${CLAUDE_SKILL_DIR}/references/platform-constraints.md before using multi-backtick fences or ! command syntax.

</platform_constraints>

<xml_tag_formatting>

Always add a blank line before a closing pseudo-XML tag that follows an unordered list. Without it, markdown parsers indent the closing tag as part of the last list item.

# ❌ WRONG

<section>

- Item 1
- Item 2

</section>

# ✅ CORRECT

<section>

- Item 1
- Item 2

</section>

Enforced by the fix-xml-spacing pre-commit hook (scripts/fix-xml-spacing.py).

</xml_tag_formatting>

<script_standards>

Skills that ship scripts/ must validate inputs with verbose, deterministic, actionable error messages and test every script before inclusion. The full validation-message and script-testing rules live in ${CLAUDE_SKILL_DIR}/references/script-standards.md. Read it before authoring a skill that bundles scripts.

</script_standards>

name	skill-standards
user-invocable	false
description	Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.
allowed-tools	Read

<reference_note> This is a reference skill. /create-skills and /audit-skills load these standards automatically. Do not invoke directly. </reference_note>

<skill_organization>

Skills follow a reference pattern to avoid duplication:

Foundational skill (e.g., /test) — core principles and domain-agnostic patterns.
Language-specific skills (e.g., /test-python, /test-typescript) — reference the foundational skill, provide only language-specific implementations.
Reference skills (e.g., /typescript-standards, /skill-standards) — standards loaded by other skills, never invoked directly.

For language-specific skills that reference a foundation, use unqualified names (/test) so they resolve to whichever foundational skill is installed.

Skill invocation limitations: Skills cannot automatically invoke other skills. They can:

Instruct Claude to read another skill file first
Reference foundational concepts by skill name
Be invoked sequentially by the user or Claude

</skill_organization>

Field	Required	Constraint
`name`	No	Lowercase letters, numbers, hyphens. ≤64 chars. Must match the directory name when set. If omitted, the directory name is used.
`description`	Recommended	Directive style for invoked skills (see `<descriptions>`); passive for references. Combined with `when_to_use` the listing is capped at 1,536 chars; put the key trigger first.
`when_to_use`	No	Extra trigger phrases or example requests appended to `description` in the skill listing. Shares the 1,536-char cap.
`argument-hint`	No	Free-text hint shown during `/` autocomplete (e.g. `[issue-number]`).
`arguments`	No	Named positional arguments for `$name` substitution in the body. Space-separated string or YAML list; names map to argument positions in order.
`allowed-tools`	No	Tools Claude may use without per-call approval while the skill is active. Space-separated string or YAML list. Restrict for audit (read-only) and reference skills.
`disable-model-invocation`	No	`true` to block programmatic invocation entirely — Claude cannot load the skill, including via the Skill tool, and the skill cannot be preloaded into subagents. Use for `/deploy`-style user-only commands. Default `false`.
`user-invocable`	No	`false` to hide from the `/` autocomplete menu while keeping Claude able to invoke via the Skill tool. Description stays in context. Use for reference skills that other skills load programmatically. Default `true`.
`model`	No	Model override for this skill (`opus`, `sonnet`, `haiku`, or `inherit`). Marketplace verification-sensitive surfaces use explicit `sonnet` and never use session inheritance.
`effort`	No	Effort level (`low`, `medium`, `high`, `xhigh`, `max`) — overrides the session effort while the skill is active.
`context`	No	`fork` to run the skill in a forked subagent context. Combine with `agent`.
`agent`	No	Subagent type to use when `context: fork` is set (`Explore`, `Plan`, `general-purpose`, or a custom agent). Defaults to `general-purpose`.
`hooks`	No	Hooks scoped to this skill's lifecycle. See the Claude Code hooks reference for shape.
`paths`	No	Glob patterns that limit auto-activation to matching files. Comma-separated string or YAML list.
`shell`	No	`bash` (default) or `powershell` for the skill's inline and fenced command-injection blocks. The `powershell` value requires `CLAUDE_CODE_USE_POWERSHELL_TOOL=1`.

Frontmatter	User `/skill`	Claude (Skill tool)	Subagent preload	Automation re-entry	Description in context
(default)	Yes	Yes	Yes	Yes	Always
`disable-model-invocation: true`	Yes	No	No	Yes	Not in context
`user-invocable: false`	No	Yes	Yes	No	Always

Pick the gate by role:

A reference skill another SKILL.md loads via the Skill tool, or a background-knowledge skill, uses user-invocable: false — hidden from the / menu, still loadable by Claude and preloadable into subagents.
A user-only side-effecting command (/deploy) uses disable-model-invocation: true. NEVER set it on a skill other skills or subagents must load: it blocks the Skill-tool call (surfacing Skill <name> cannot be used with Skill tool due to disable-model-invocation) AND blocks subagent preloading.
A skill any automation loop re-enters — a scheduled wakeup, heartbeat, or /loop target — MUST be user-invocable (leave the default; never user-invocable: false). Automation fires as a user-style prompt, so user-invocable: false rejects it and no Claude-private heartbeat exists to bypass that. When a loop body is otherwise reference-like, expose a user-invocable entry the loop targets rather than gating the body. Such a loop body keeps a passive description — it is invoked by exact name (the timer or a parent skill), not by description-match, so a directive description would only cause false auto-activations. A user-invocable skill with a passive description is the correct shape here, not a defect.

# Invoked skill (routing, workflow, creation)
---
name: create-skills
description: >-
  ALWAYS invoke this skill when creating, editing, or improving SKILL.md files.
  NEVER create or modify skills without this skill.
---

# Reference skill (standards, loaded programmatically by other skills)
---
name: skill-standards
user-invocable: false
description: >-
  Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.
allowed-tools: Read
---

# User-only command (side effects; Claude must not auto-trigger)
---
name: deploy
disable-model-invocation: true
description: Deploy the application to production
allowed-tools: Bash(git *) Bash(./deploy *)
---

Audit skills (audit-*) must add allowed-tools: Read, Grep, Glob, Bash per the read-only rule for audit skills — audit runs never modify files.

Directory match is mandatory. skills/author/ → name: author. A mismatch breaks skill lookup.

<naming_conventions>

The name field is the user invocation path (/skill-name). Match user speech patterns.

Rules:

Use domain acronyms: author not author-spec-tree-artifacts
Use terms users actually say: test-python not python-unit-test-framework
Think "CD-ROM" not "Compact Disc Read Only Memory"
Directory name MUST match: skills/author/ → name: author

Naming form: invoked workflow skills use imperative verbs. Reference skills use noun phrases ending in the domain they standardize, such as skill-standards or typescript-test-standards.

Treat generated runtime output and implementation names as lower-layer evidence, never as the authority for vocabulary classification.

Material-change rule: Any material change to a skill implies renaming all skills in the entire plugin to match the latest develop rules.

# ✅ Matches user speech
name: author # Users say "author a spec"
name: test-typescript # Users say "test TypeScript code"
name: bootstrap # Users say "bootstrap the spec tree"

# ❌ Nobody says these
name: author-spec-tree-artifacts # Too verbose
name: typescript-unit-framework # Wrong order

</naming_conventions>

The description field governs skill selection. Claude has a character budget for all skill metadata — when exceeded, skills become invisible.

Activation rates by style (Seleznov, 650 automated trials, Feb 2026):

Style	Activation	Pattern
Passive	~77%	`Use when…`
Expanded	~93%	`…or any X-related task`
Directive	~100%	`ALWAYS invoke… NEVER X without`

Use directive descriptions for invoked skills:

description: >-
  ALWAYS invoke this skill when <triggers>.

NEVER constraint — add only when it disambiguates. A NEVER line helps when:

The skill is the only one with that negative (e.g., NEVER work on the spec tree without loading context — only contextualizing says this).
Claude has a strong built-in alternative the negative prevents (e.g., NEVER run git commit without this skill — Claude would just run git commit directly).

Omit NEVER when multiple skills share the same negative (adds noise) or the ALWAYS trigger is already specific enough.

Language-after-artifact (matches user speech):

# ✅ "audit ADRs for Python"
ALWAYS invoke this skill when auditing ADRs for Python.

# ❌ "audit Python ADRs"
ALWAYS invoke this skill when auditing Python ADRs.

Match user speech over formal jargon: Use abbreviations users would use (ADR not Architecture Decision Record). Avoid corporate speak.

Reference skills use user-invocable: false with a passive description:

user-invocable: false
description: >-
  Python code standards enforced across all skills. Loaded by other skills, not invoked directly.

description: >-
  Test-evidence audit methodology preloaded by the test-evidence-auditor agent.
  Dispatch test-evidence-auditor to audit test evidence; the main conversation
  reaches this audit only through that agent.

Conflict resolution: If Claude picks the wrong skill, descriptions are too similar. Make trigger terms distinct — "sales data in Excel" vs "log files and system metrics".

<xml_structure>

Skills use pure XML structure — no markdown headings (#, ##, ###) anywhere in the body. Keep markdown formatting within content (bold, italic, lists, tables, code blocks, links).

Why pure XML: unambiguous section boundaries, consistent cross-skill structure, better token efficiency, better Claude performance.

Required tags (every skill):

Tag	Content
`<objective>`	The observable output the skill produces, in a definite shape — one sentence, not an actor or an activity, not a summary of the skill. See `/agent-prompt-standards` `<objective_shape>`.
`<success_criteria>`	The properties that prove the output is sound — not a re-list of the workflow steps.

Router-pattern tags (skills that route to multiple workflows):

Tag	Content
`<essential_principles>`	Principles that apply regardless of which workflow runs. Inline.
`<intake>`	Question to ask the user to determine routing.
`<routing>`	Table mapping responses to workflow files.
`<reference_index>`	List of available reference files.
`<workflows_index>`	List of available workflow files.

Workflow-file tags (files inside workflows/):

Tag	Content
`<required_reading>`	Which reference files to load before running this workflow.
`<process>`	Step-by-step procedure.
`<success_criteria>`	When this workflow is complete.

Conditional tags (include when the skill's complexity or purpose calls for them):

Tag	When to include
`<quick_start>`	On-demand tool skills with a meaningful fast path. Omit for foundation, gate, validator, and reference skills — completeness is the point.
`<dispatch_gate>`	Agent-preloaded audit skills. A hard stop at the top of the body that halts a main-conversation invocation and directs it to dispatch the corresponding auditor agent. Omit for every other skill type.
`<context>`	Background needed before starting.
`<workflow>`	Sequential steps (non-router skills).
`<advanced_features>`	Progressive disclosure for deep-dive topics.
`<validation>`	Verification checks.
`<examples>`	Input/output pairs.
`<anti_patterns>`	Common mistakes to avoid.
`<security_checklist>`	Skills with security implications.
`<testing>`	Testing workflows or validation steps.
`<common_patterns>`	Reusable recipes.
`<reference_guides>`	Pointers to detailed reference files.
`<failure_modes>`	Named failures from actual usage — what happened, why, how to avoid.

Nesting: XML tags can nest for hierarchical content.

<examples>
  <example number="1">
    <input>User input</input>
    <output>Expected output</output>
  </example>
</examples>

Close every tag. Unclosed tags break parsing.

Constraints:

Filter expensive commands (spx session list --status doing,todo, git log -10, head -N) so output stays bounded.
Move data into the workflow file that actually consumes it when the skill loader doesn't need it for trigger evaluation. The <context> block is for trigger-time orientation, not workflow inputs.
Avoid commands whose output grows monotonically (archives, full caches, full file trees).

Semantic names: <workflow> not <steps>, <success_criteria> not <done>, <anti_patterns> not <dont_do>.

Reference tags in prose by name: "Using the schema in <schema> tags…", "Follow the workflow in <workflow>…". Makes structure self-documenting.

Intelligence rules — match structure to complexity:

Skill class	Expected tags
Simple (single domain)	`<objective>`, `<success_criteria>`, optionally `<quick_start>`
Medium (multiple patterns)	Required + `<workflow>` and/or `<examples>`
Complex (multi-domain, API, sec)	Required + router pattern + appropriate conditional tags
Foundation / gate / validator / reference	Required + `<workflow>`. Omit `<quick_start>` — no abbreviated path exists.
Auditor (agent-preloaded)	The canonical auditor skeleton — read `references/auditor-skeleton.md` when authoring or auditing an `audit-` skill. Omit* `<quick_start>`.

Don't over-engineer simple skills. Don't under-specify complex ones.

</xml_structure>

<progressive_disclosure>

SKILL.md is an overview. Reference files carry detail. Claude loads reference files only when needed.

Rules:

Keep SKILL.md under 500 lines.
References live in references/ one level deep from SKILL.md. Do not nest references that read other references — Claude may only partially read transitive files.
Reference files over 100 lines need a table of contents at the top, so partial reads still see the full scope.
Use forward slashes in every path — references/guide.md, never references\guide.md. Works across platforms.

Token efficiency: simple task loads SKILL.md only (~500 tokens); medium loads SKILL.md + one reference (~1000); complex loads SKILL.md + multiple (~2000+).

✅ One level deep
SKILL.md → references/advanced.md (complete info)
         → references/examples.md (complete info)

❌ Nested
SKILL.md → references/advanced.md → references/details.md → actual info

Name reference files descriptively — xml-structure-examples.md, not examples.md. The filename is also a table-of-contents entry in <reference_index>.

</progressive_disclosure>

The context window is shared. A skill competes for tokens with the system prompt, conversation history, other skills' metadata, and the user's request.

Test every sentence: "Does removing this reduce Claude's effectiveness at the task?" If no — cut it.

What Claude already knows (never include):

General programming knowledge
Language syntax and standard-library APIs
Common design patterns
How to use its own tools

What Claude needs (include):

Product-specific conventions that contradict common patterns
Domain knowledge not in training data
Failure modes from actual usage (not hypotheticals)
Verification commands and thresholds

Concrete over abstract:

❌ "Ensure coverage is maintained"
✅ "Coverage delta must be ≤0.5%. Run: pnpm test --coverage | grep target.ts"

When to elaborate: the concept is domain-specific (not general programming), the pattern is non-obvious or counterintuitive, or context affects behavior in subtle ways.

<skill_types>

Six skill types. Each has a distinct purpose and primary output.

Type	Purpose	Primary output	Key sections
Builder	Create new artifacts	Code, documents, widgets, configs	Required clarifications, output spec, domain standards, templates in `assets/`
Guide	Teach procedures	Step-by-step workflows, tutorials	Numbered workflow, input→output example pairs, decision trees
Automation	Execute multi-step processes	Processed files, transformed data	Tested scripts in `scripts/`, error handling, dependencies, I/O contracts
Analyzer	Extract insights	Reports, summaries, reviews	Analysis scope, evaluation criteria, output format, synthesis
Validator	Enforce quality	Pass/fail verdicts, scores	Criteria with thresholds, scoring rubric, remediation guidance; `user-invocable: false` when invoked only by agents or explicit `Skill(name)` calls
Reference	Share domain knowledge	Standards loaded by other skills	`user-invocable: false`, passive description, `allowed-tools: Read`

Type-selection rule of thumb:

Creates new artifacts → Builder
Teaches how-to → Guide
Executes processes → Automation
Extracts insights → Analyzer
Checks quality → Validator
Shares knowledge multiple skills need → Reference

</skill_types>

<reference_skills>

Reference skills hold shared domain knowledge that multiple skills need. They are not invoked directly — consuming skills reach them via /skill-name references in their text.

Required frontmatter:

---
name: {domain}-standards
user-invocable: false
description: >-
  {Domain} standards enforced across all skills. Loaded by other skills, not invoked directly.
allowed-tools: Read
---

user-invocable: false — prevents false activations from user prompts.
Passive description (no ALWAYS/NEVER) — directive descriptions trigger false activations for a reference.
allowed-tools: Read — reference skills only read.

How consuming skills reference it. Write the reference skill path in running text; Claude loads the reference into context on encounter.

# In test-typescript/SKILL.md:

See `/typescript-test-standards` for test file naming, execution levels, and reusable test patterns.

# In audit-typescript-tests/SKILL.md:

Before auditing, read `/typescript-test-standards` for the complete catalog of TypeScript test rules.

Naming convention: {domain}-standards for standards. Examples: typescript-test-standards, skill-standards, agent-prompt-standards.

Anti-patterns:

Directive descriptions (ALWAYS/NEVER) — cause false activations.
Shared content buried in one skill's references/ — ${CLAUDE_SKILL_DIR} is isolated per skill.
Same content duplicated across multiple references/ — drifts.
Partial extraction: naming a new standards skill while leaving the meat in the builder's references/ — the auditor keeps reading the old location and the rename becomes a lie.

</reference_skills>

<templates_and_variables>

</templates_and_variables>

<platform_constraints>

</platform_constraints>

<xml_tag_formatting>

Always add a blank line before a closing pseudo-XML tag that follows an unordered list. Without it, markdown parsers indent the closing tag as part of the last list item.

# ❌ WRONG

<section>

- Item 1
- Item 2

</section>

# ✅ CORRECT

<section>

- Item 1
- Item 2

</section>

Enforced by the fix-xml-spacing pre-commit hook (scripts/fix-xml-spacing.py).

</xml_tag_formatting>

<script_standards>

</script_standards>