skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
69
57%
Does it follow best practices?
Impact
85%
1.21xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/skill-creator/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is competent with a clear 'Use when' clause and reasonable domain identification. However, it lacks specific concrete actions (e.g., generating frontmatter, validating skill structure) and could include more natural trigger terms that users would actually say. The distinctiveness is moderate—'AgentSkills' helps but the surrounding language is generic enough to risk overlap.
Suggestions
Add more specific concrete actions like 'generate YAML frontmatter, create script files, validate skill structure' to improve specificity.
Include additional natural trigger terms users might say, such as 'SKILL.md', 'skill template', 'skill file', 'new skill', or 'skill definition'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('AgentSkills') and some actions ('create or update', 'designing, structuring, packaging'), but the actions are somewhat generic and don't list concrete specific operations like 'write YAML frontmatter', 'generate script files', or 'validate skill format'. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or update AgentSkills with scripts, references, and assets) and 'when' (Use when designing, structuring, or packaging skills). The 'Use when...' clause is explicitly present with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'skills', 'scripts', 'references', 'assets', 'packaging', but misses natural variations users might say such as 'skill file', 'SKILL.md', 'skill template', 'new skill', or 'skill definition'. 'AgentSkills' is a somewhat specialized term that users may or may not use naturally. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'AgentSkills' provides some distinctiveness, but 'designing, structuring, or packaging' with 'scripts, references, and assets' is broad enough that it could overlap with general project scaffolding or template-creation skills. The niche is somewhat clear but not sharply delineated. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a well-structured workflow with clear sequential steps and good references to external files, but suffers significantly from verbosity. It extensively explains concepts Claude already understands (what skills are, what scripts/references/assets directories contain, basic design principles) and includes lengthy examples that could be condensed. The actionable content (init_skill.py and package_skill.py commands) is buried within walls of explanatory text.
Suggestions
Cut the 'About Skills' and 'What Skills Provide' sections entirely—Claude already knows what skills are. Start directly with the anatomy/structure and creation process.
Move the 'Progressive Disclosure Design Principle' section with its multiple pattern examples into a references/progressive-disclosure.md file, keeping only a brief summary and link in SKILL.md.
Condense the 'Core Principles' section to bullet points rather than multi-paragraph explanations—the bridge/field metaphor and detailed rationale for degrees of freedom are unnecessary.
Make Step 4 (Edit the Skill) more actionable by providing a concrete SKILL.md template or checklist rather than abstract writing guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose, explaining many concepts Claude already knows (what skills are, what PDFs are, what scripts/references/assets mean). It includes extensive explanations of basic concepts like 'progressive disclosure' and 'degrees of freedom' that pad the content significantly. Much of this could be condensed to a fraction of its current length. | 1 / 3 |
Actionability | The skill provides concrete commands for init_skill.py and package_skill.py with usage examples, which is actionable. However, the actual SKILL.md writing guidance is largely abstract ('write instructions for using the skill'), and the bulk of the content describes concepts rather than providing executable, copy-paste-ready guidance for creating skills. | 2 / 3 |
Workflow Clarity | The 6-step skill creation process is clearly sequenced with explicit steps (Understand → Plan → Initialize → Edit → Package → Iterate). Each step includes when to skip it, what to do, and validation is built into the packaging step. The workflow is well-structured with clear progression and feedback loops in Step 6. | 3 / 3 |
Progressive Disclosure | The skill references external files (references/workflows.md, references/output-patterns.md) which is good progressive disclosure. However, the SKILL.md body itself is a monolithic wall of text (~500+ lines) with extensive inline content that could be split into reference files. The detailed examples of directory structures and patterns could live in separate references. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- attilaczudor/Test
- Commit
b3cef5f
- 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.