make-skill

name	make-skill
description	Creates new repo-native skills from plan to scaffolded `SKILL.md` and catalog entry. Use when adding a skill to this repository.
user-invocable	true
disable-model-invocation	true

Make Skill

Core Contract

Create one new skill in this repository, including compliant SKILL.md and README.md catalog entry. Default location is skills/<category>/<name>/SKILL.md; use .agents/skills/ only when explicitly requested. Start with a brief plan and explicit assumptions. Follow CLAUDE.md / AGENTS.md on conflict.

SKILL.md Contract

SKILL.md must include required frontmatter keys:

name: skill-name
description: One terse sentence describing the desired outcome of this skill. Second sentence describing conditions that should invoke this skill.
user-invocable: true
disable-model-invocation: false

• name: lowercase-hyphenated and must match the skill directory name.
• description: third person, outcome-first, ends with Use when ....
• user-invocable: default true unless explicitly constrained.
• disable-model-invocation: default false unless explicitly constrained.

Body sections should use this default order when relevant:

1. # Title
2. ## Core Contract (include scope/tools; target repo CLAUDE.md or AGENTS.md overrides on conflict)
3. ## Required Inputs
4. ## Workflow (numbered, with stop-and-ask gates)
5. ## <Platform> Implementation Notes (concrete commands)
6. ## Safety Rules (Never ... constraints)
7. ## Output Style

Omit irrelevant sections rather than adding filler.

Required Inputs

1. Skill purpose/workflow.
2. Target category.
3. Proposed name (if any).
4. Required tools, constraints, and safety rules.
5. Output/reporting expectations.

Workflow

1. Restate request and produce a compact creation plan.
2. List assumptions (safe default vs needs confirmation).
3. Ask only high-impact clarifying questions.
4. Normalize/derive name and validate with check-skill-name.
5. Create SKILL.md in confirmed location with required conventions.
6. Add concise README.md catalog entry.
7. Verify naming alignment and section/policy compliance.

Stop and ask if request spans multiple skills, name is not CLEAR, or ambiguity changes behavior/safety.

Safety Rules

• Never scaffold files before the skill name is CLEAR via check-skill-name.
• Never hide assumptions; always label them and confirm high-impact ones.
• Never ask location-clarification by default; assume global unless the user directly requests repo-local.
• Never skip clarifying questions when ambiguity affects behavior, tooling, or safety (excluding default location).
• Never violate required repository conventions for frontmatter and section ordering.
• Never silently broaden scope beyond one requested skill without user approval.
• Never leave README.md out of sync after adding, renaming, or removing a skill.

Output Style

Report final category/name and name-check verdict, files changed, assumptions confirmed, defaults applied, and optional next improvements.