create-skill-reference

name	create-skill-reference
description	Create and refine high-quality Agent Skills. Use when drafting, reviewing, or updating a skill, deciding what belongs in SKILL.md versus bundled resources, or turning a repeated workflow into reusable agent instructions.

Create Skill Reference

Use this skill to create skills that are easy to trigger, easy to inspect, and useful across repeated tasks.

Workflow

1. Identify the repeated job the skill should make easier.
2. Decide when the skill should trigger and put that guidance in the description.
3. Keep SKILL.md as the routing and workflow layer.
4. Move details into references/ when they are useful for some tasks but not all tasks.
5. Put deterministic or repeatedly rewritten work in scripts/.
6. Put reusable output resources, templates, examples, or lookup tables in assets/.
7. Add lightweight evaluation prompts or acceptance checks when the skill has observable outputs.
8. Validate the skill with the host repository's standard skill checks.

Skill Standards

• Create a coherent unit around a real repeated workflow, not a vague topic.
• Use a lowercase hyphenated name that matches the skill folder.
• Write a description that says what the skill does and when to use it; this is the primary trigger surface.
• Prefer direct, imperative instructions that explain the reason behind important constraints.
• Keep SKILL.md concise enough to inspect quickly. Move conditional, domain-specific, or bulky material into bundled resources.
• Reference bundled files with clear guidance about when to read or use them.
• Add a bundled file only when it saves future context, reduces repeated work, preserves source truth, or provides a reusable output resource.
• Explain source boundaries. If data comes from a curated asset instead of an API or source document, say so.
• Preserve the skill's original name when updating an existing skill unless the user explicitly wants a rename.
• Update the skill when repeated corrections reveal a better reusable practice.

Resource Placement

• Use references/ for detailed instructions, API notes, schemas, examples, rubrics, or domain-specific variants.
• Use scripts/ for repeatable commands, conversions, queries, validators, generators, or other deterministic work.
• Use assets/ for templates, sample files, lookup tables, images, fonts, or other reusable output material.
• Avoid adding resources that SKILL.md never routes to.

References

• Read references/skill-checklist.md before creating or substantially revising a skill.