skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
81
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/skillEvaluation — 85%
↑ 1.21xAgent success when using this skill
Validation for skill structure
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 has good structure with an explicit 'Use when...' clause that clearly separates what from when. However, it lacks specific concrete actions beyond 'create or update' and could benefit from more natural trigger terms that users would actually say. The domain is somewhat specialized but the supporting terms are generic enough to risk overlap.
Suggestions
Add more specific concrete actions like 'generate YAML frontmatter, write skill instructions, organize supporting scripts and assets'
Include additional natural trigger terms users might say: 'SKILL.md', 'skill file', 'skill template', 'new skill', 'agent capability'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AgentSkills) and some actions ('Create or update', 'designing, structuring, or packaging'), but lacks comprehensive detail about what specific operations are performed (e.g., generating YAML frontmatter, writing markdown content, organizing file structures). | 2 / 3 |
Completeness | Clearly answers both what ('Create or update AgentSkills') and when ('Use when designing, structuring, or packaging skills with scripts, references, and assets') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('skills', 'scripts', 'references', 'assets', 'packaging') but misses common variations users might say like 'SKILL.md', 'skill file', 'skill template', 'skill definition', or 'agent capability'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'AgentSkills' provides some specificity, but 'scripts, references, and assets' is generic enough to potentially overlap with general file management or documentation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%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 meta-skill that provides comprehensive guidance for creating skills. Its main strength is the clear, actionable 6-step workflow with concrete script commands and validation steps. The primary weakness is verbosity in the introductory sections that explain concepts Claude likely already understands, though this is partially justified given the skill teaches others how to write concise skills.
Suggestions
Condense the 'About Skills' and 'What Skills Provide' sections - Claude understands what modular packages are; focus on what's unique to this skill system
Move the 'Core Principles' section content to a references file since it's conceptual guidance rather than procedural instruction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains valuable information but is verbose in places, explaining concepts like 'what skills provide' and 'core principles' that could be more condensed. Some sections like 'About Skills' explain things Claude likely already understands about modular packages. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific script commands (init_skill.py, package_skill.py), clear directory structures, and copy-paste ready examples. The step-by-step process is fully actionable with real commands and file paths. | 3 / 3 |
Workflow Clarity | The 6-step skill creation process is clearly sequenced with explicit validation (Step 5 packaging validates automatically). Each step has clear entry/exit criteria, and the workflow includes feedback loops ('Iterate based on real usage'). | 3 / 3 |
Progressive Disclosure | Excellent structure with clear references to external files (references/workflows.md, references/output-patterns.md) that are one level deep. The skill itself teaches progressive disclosure patterns and follows them well with organized sections. | 3 / 3 |
Total | 11 / 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.
- 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.