create-skill

Create Skill

Required resources and checks

• Before using a starter, read and adapt assets/skill-template.md. Replace every sentinel and remove unused sections.
• Before finalizing or reviewing, read references/skill-quality-checklist.md. Record applicable evidence.
• When this catalog's root scripts exist, run:
  • node scripts/validate-skill-metadata.mjs <skill-path>
  • node scripts/validate-skill-links.mjs <skill-path>
• Otherwise perform equivalent checks manually. Report the unavailable gate.

Follow user and higher-priority constraints. Keep one coherent job. Preserve behavior outside an evidence-backed requested change.

Skill contract

• Put all activation guidance in frontmatter description. The body loads only after activation.
• Use: [Third-person capability]. Use this skill when [intents/triggers]. Do not use when/for [material near misses].
• Keep the description under 1024 characters. Focus on intent, outcomes, and adjacent boundaries—not mechanics.
• Keep SKILL.md concise and actionable. Put critical constraints, mandatory resources, fragile sequencing, validation, and safety early.
• Default to short headings, compact bullets, numbered procedures, and small tables. Use prose paragraphs only when they communicate necessary nuance more clearly.
• Keep each bullet focused on one instruction or tightly coupled behavior. Prefer direct wording; remove throat-clearing, repeated rationale, and paragraph-length bullets.
• Match the surrounding skill catalog's density. A longer main file requires execution-critical justification; move conditional detail into references/.
• Use progressive disclosure deliberately. Do not squeeze useful reusable detail into SKILL.md merely to avoid a resource.
• Use references/ for detailed workflows, schemas, examples, tool guidance, and gotchas.
• Use assets/ for reusable templates and static output shapes.
• Use scripts/ for repeated or fragile deterministic operations.
• Add resources when they improve repeated execution, clarity, consistency, or maintenance.
• Keep references one level deep.
• Add a resource pointer only after its file exists. Give its exact path, purpose, and read/use/run condition.
• Repeat mandatory resource loading at the relevant workflow step. Delete stale pointers and empty directories.
• Refer to other skills by name, such as create-plan. Do not use relative paths to their SKILL.md files.
• Ground changes in real tasks, artifacts, recurring failures, user corrections, or evaluation evidence.
• Reject one-off or speculative preferences. Prefer the smallest durable correction.
• Check tools, schemas, commands, and examples for staleness. Ask when reusability is unclear.
• Prescribe fragile, destructive, security-sensitive, and validation-critical sequences. Allow judgment elsewhere.