skill-creator
Design effective Claude Code skills with optimal descriptions, progressive disclosure, and error prevention patterns. Covers freedom levels, token efficiency, and quality standards. Use when: creating new skills, improving skill descriptions, optimizing token usage, structuring skill content, or debugging why skills aren't being discovered.
84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 skill description with excellent completeness and distinctiveness. The explicit 'Use when:' clause with multiple trigger scenarios is well-crafted. The main weakness is that the capabilities section uses somewhat abstract concepts (progressive disclosure, freedom levels) rather than concrete action verbs.
Suggestions
Rephrase capabilities with more concrete action verbs, e.g., 'Write effective skill descriptions, structure content with progressive disclosure, implement error prevention patterns' instead of 'Design effective Claude Code skills with optimal descriptions...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude Code skills) and mentions several concepts (descriptions, progressive disclosure, error prevention, freedom levels, token efficiency) but these are somewhat abstract rather than concrete actions. Missing specific verbs like 'write', 'structure', 'validate'. | 2 / 3 |
Completeness | Clearly answers both what (design effective Claude Code skills with optimal descriptions, progressive disclosure, error prevention patterns) and when (explicit 'Use when:' clause with five specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'creating new skills', 'improving skill descriptions', 'optimizing token usage', 'structuring skill content', 'debugging why skills aren't being discovered'. These match realistic user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Claude Code skill authoring. The combination of 'skill descriptions', 'skill content', and 'skills aren't being discovered' creates a distinct trigger profile unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent concrete examples and clear workflows. Its main weakness is length - it could be more concise by moving some philosophical content and detailed examples to reference files. The good/bad comparisons and checklists are particularly effective for guiding skill creation.
Suggestions
Move the 'Token Efficiency' metrics table and 'Core Principles' philosophy sections to a references/ file, keeping only the actionable guidelines in SKILL.md
Consolidate the 'Common Mistakes' section into a more compact format or move detailed examples to references/common-mistakes.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-organized but includes some unnecessary explanation (e.g., explaining what progressive disclosure is, the 'Context Window is a Public Good' philosophy section). Some sections like 'Token Efficiency' with the metrics table add bulk without actionable value. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific character counts (250-350), exact YAML examples, bash commands, checklists with checkboxes, and clear good/bad comparisons. The code examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear multi-step processes with explicit validation: the Quality Checklist provides a comprehensive verification workflow, Testing Your Skill section has discovery and functionality tests, and the Quick Command Reference provides the exact sequence for skill creation. | 3 / 3 |
Progressive Disclosure | References external files (planning/claude-code-skill-standards.md, ONE_PAGE_CHECKLIST.md, example skills) but the main SKILL.md itself is quite long (~5k words). Some content like the full Token Efficiency section and detailed Common Mistakes could be moved to references. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.