Skill Designer is a Claude Code Skill for designing, analyzing, adapting, improving, validating, and packaging other Claude Code Skills.
It turns a rough automation idea, an existing Skill file, or a repeated workflow into a structured Skill package with clear triggers, boundaries, workflow steps, quality gates, and validation guidance.
Skill Designer supports four common workflows:
- Create from scratch — turn a rough idea into a complete Skill design.
- Reverse-engineer a Skill — analyze an existing Skill through a six-dimensional canvas.
- Remix a Skill — extract useful parts from another Skill and adapt them into a better version.
- Improve an existing Skill — refine triggers, workflow, boundaries, validation, packaging, or release readiness.
Most weak Skills fail for predictable reasons: the task is too broad, the trigger is vague, the workflow depends on intuition, or there are no quality gates. Skill Designer forces a Skill through a concrete design process before files are generated or published.
It is especially useful when you want to turn repeated Claude Code work into a reusable capability package instead of a one-off prompt.
skill-designer/
├── README.md # English GitHub homepage
├── README.zh-CN.md # Chinese documentation
├── LICENSE
├── CHANGELOG.md
├── .gitignore
├── skill/
│ └── skill-design/
│ ├── SKILL.md
│ └── references/
│ ├── skill-spec.md
│ ├── skill-6d.md
│ ├── skill-audit-23.md
│ ├── skill-validation.md
│ ├── frontmatter-compat.md
│ ├── eval-template.json
│ └── trigger-eval-template.json
└── examples/
├── example-prompt-create-skill.md
├── example-prompt-audit-skill.md
└── example-output-outline.md
Copy the installable Skill folder into your Claude Code skills directory:
cp -r skill/skill-design ~/.claude/skills/Restart Claude Code so the Skill is loaded.
Windows Git Bash note: copy the actual folder. Do not install this Skill with
ln -sunless you know your Claude Code environment handles symlinks correctly.
Use this Skill when you want to design, create, analyze, adapt, test, optimize, package, or publish a Claude Code Skill.
Example:
/skill-design
I repeatedly turn messy meeting notes into a weekly founder update. Help me design this as a reusable Claude Code Skill.
The Skill will guide the work through:
- fit assessment — whether the task should become a Skill at all;
- genre classification — tool, dialogue, or audit Skill;
- six-dimensional design canvas;
- scope trimming and boundary checks;
- naming and placement decisions;
- file generation after user confirmation;
- quality review and optional validation.
See the examples/ directory:
example-prompt-create-skill.mdexample-prompt-audit-skill.mdexample-output-outline.md
Use Skill Designer when:
- you repeat a Claude Code workflow every day or every week;
- you want to convert a SOP, checklist, or decision process into a reusable Skill;
- you have an existing Skill that triggers poorly or produces inconsistent results;
- you want to package a Skill for sharing or open-source release;
- you need clear quality gates before trusting a Skill.
Skill Designer is not intended for:
- one-off prompts that do not need reuse;
- ordinary article writing or content drafting;
- small Markdown edits;
- full multi-agent team architecture;
- irreversible or high-risk automation that should remain under human control.
The Skill is built around a six-dimensional canvas:
| Dimension | Question |
|---|---|
| Scenario | What exact repeated task does this Skill solve? |
| System | What stable workflow, SOP, or decision tree drives the Skill? |
| Data | What inputs, outputs, and examples does it need? |
| Tools | What Claude Code tools or external scripts does it use? |
| Taste | What makes the output good or bad? |
| Creativity | What core assumption makes this workflow effective? |
It also includes a 23-point audit checklist, frontmatter compatibility guidance, and optional validation workflow for testing trigger accuracy and real usefulness.
The included SKILL.md uses Claude Code native frontmatter fields so it is suitable for sharing and general validation. Extended local routing metadata should be kept in the body or references rather than added to the frontmatter.
MIT