skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
65
51%
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 functional and covers both what and when, earning good marks on completeness. However, it lacks concrete specificity about what creating/updating an AgentSkill actually entails (e.g., YAML frontmatter, markdown structure, file organization), and the trigger terms could be more natural and varied to help Claude distinguish this skill from general project scaffolding or documentation tasks.
Suggestions
Add more concrete actions like 'write YAML frontmatter, generate script files, organize asset directories, define skill metadata'
Include more natural trigger terms users might say, such as 'SKILL.md', 'skill template', 'new skill file', 'skill definition', or 'skill configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('AgentSkills') and some actions ('create or update', 'designing, structuring, packaging'), but doesn't list concrete specific actions like 'write YAML frontmatter', 'generate script files', or 'organize asset directories'. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or update AgentSkills with scripts, references, and assets) and 'when' (explicit 'Use when designing, structuring, or packaging skills'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'skills', 'scripts', 'references', 'assets', 'packaging', but misses natural user phrases like 'skill file', 'SKILL.md', 'skill template', 'new skill', or 'skill definition'. 'AgentSkills' is a specific term but may not be what users naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'AgentSkills' provides some distinctiveness, but 'scripts, references, and assets' is broad enough to potentially overlap with general project scaffolding or documentation skills. The word 'skills' alone could conflict with other skill-related tools. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive meta-skill for creating skills, but it suffers significantly from verbosity—it explains many concepts Claude already understands (what skills are, what scripts/references/assets mean, basic organizational principles). The actionable parts (init_skill.py, package_skill.py commands, 6-step workflow) are solid but buried in explanatory prose. The skill would benefit greatly from aggressive trimming and better practicing the conciseness principle it preaches.
Suggestions
Cut the 'About Skills' and 'What Skills Provide' sections entirely—Claude already knows what skills are. Start directly with 'Core Principles' or the creation process.
Reduce the 'Bundled Resources' section to a concise table (type | when to use | example) instead of verbose paragraphs for each resource type.
Move the detailed progressive disclosure patterns and examples into a separate references/progressive-disclosure.md file, keeping only a brief summary in SKILL.md—practice what the skill preaches.
Add an explicit validation checkpoint between Step 4 (Edit) and Step 5 (Package), such as a checklist: verify scripts run, verify references are linked from SKILL.md, verify SKILL.md is under 500 lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, extensively explaining concepts Claude already knows (what skills are, what PDFs are, what scripts/references/assets mean). Sections like 'What Skills Provide' and 'About Skills' are unnecessary preamble. The 'What to Not Include' section lists obvious items. Much of this could be cut by 60-70% without losing actionable content. | 1 / 3 |
Actionability | The skill provides concrete commands for init_skill.py and package_skill.py with executable examples, and the 6-step process is reasonably specific. However, the SKILL.md body writing guidance is vague ('Write instructions for using the skill'), and many sections describe concepts rather than giving copy-paste-ready instructions. The actual skill creation steps mix actionable commands with abstract advice. | 2 / 3 |
Workflow Clarity | The 6-step process is clearly sequenced and each step has a defined purpose with skip conditions. However, validation is only mentioned as part of the packaging step (Step 5), and there are no explicit checkpoints between steps 3-4 to verify resources work correctly before proceeding. The instruction to test scripts is mentioned but lacks a concrete validation command or feedback loop structure. | 2 / 3 |
Progressive Disclosure | The skill references two external files (references/workflows.md and references/output-patterns.md) with clear descriptions of when to consult them, which is good. However, the SKILL.md itself is monolithic and contains extensive inline content that could be split out (e.g., the detailed progressive disclosure patterns, the planning examples, the naming conventions). The skill teaches progressive disclosure but doesn't fully practice it. | 2 / 3 |
Total | 7 / 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
b4fc4af
- 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.