skill-creator
Scaffold a new Claude Code skill with SKILL.md, frontmatter, and bundled resources. Use when creating a custom skill, standardizing skill structure across a team, or packaging a skill for distribution.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skills/skill-creator/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both what the skill does and when to use it, with a well-defined niche. The trigger terms are natural and specific to the domain. The main weakness is that the 'what' portion could be slightly more detailed about the concrete actions performed during scaffolding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude Code skill creation) and some actions ('scaffold', 'SKILL.md', 'frontmatter', 'bundled resources'), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify what scaffolding entails beyond naming file components. | 2 / 3 |
Completeness | Clearly answers both 'what' (scaffold a new Claude Code skill with SKILL.md, frontmatter, and bundled resources) and 'when' (creating a custom skill, standardizing skill structure across a team, or packaging a skill for distribution) with explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'skill', 'SKILL.md', 'custom skill', 'skill structure', 'packaging a skill', 'frontmatter', 'scaffold'. These are terms a user would naturally use when wanting to create a new skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche—scaffolding Claude Code skills with SKILL.md files. Unlikely to conflict with other skills due to the highly specific domain of skill creation and the distinct trigger terms like 'SKILL.md', 'frontmatter', and 'skill structure'. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of how to scaffold a new Claude Code skill, with a clear directory structure and a useful SKILL.md template. However, it references scripts (init_skill.py, package_skill.py) that don't exist in the bundle, undermining actionability. The content could be more concise by removing the organizational patterns table and tightening the tips section.
Suggestions
Provide the referenced scripts (init_skill.py, package_skill.py) as bundle files, or remove references to them and replace with inline executable commands
Add a feedback loop to the validation step: specify what to do when each check fails (e.g., 'If frontmatter name is not kebab-case, rename using...')
Move the organizational patterns table to a references/ file to reduce SKILL.md size and improve progressive disclosure
Remove or condense the 'When to Use' section since it largely duplicates the frontmatter description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the organizational patterns table and the 'When to Use' section that largely restates the description. The tips section is useful but some items are obvious. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | References scripts like `init_skill.py` and `package_skill.py` but no bundle files are provided, making these non-executable. The SKILL.md template is concrete and useful, but the workflow relies on scripts that don't exist in the bundle. The example is a walkthrough rather than copy-paste ready code. | 2 / 3 |
Workflow Clarity | The 4-step workflow (Create → Template → Validate → Package) is clearly sequenced, and the validation step includes a checklist. However, there's no feedback loop for validation failures — it says 'verify' but doesn't describe what to do if checks fail, and the validation is more of a checklist than an executable verification step. | 2 / 3 |
Progressive Disclosure | The content references scripts and directories (scripts/, references/, assets/) but no bundle files are provided to support them. The SKILL.md itself is reasonably structured with clear sections, but it's somewhat monolithic — the organizational patterns table and the full template example could be in separate reference files. Without actual bundle files, the references to scripts are hollow. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Commit
60a4372
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.