skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
83
Quality
76%
Does it follow best practices?
Impact
92%
2.13xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/skill-creator/SKILL.mdDiscovery
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 adequately covers the what and when with an explicit trigger clause, earning full marks for completeness. However, it lacks specific concrete actions beyond high-level verbs and could benefit from more natural trigger terms that users would actually say. The distinctiveness is moderate due to somewhat generic supporting terminology.
Suggestions
Add more specific concrete actions like 'generate YAML frontmatter, write skill instructions, organize asset directories'
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... with scripts, references, and assets') and when ('Use when designing, structuring, or packaging skills') 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 for creating skills, with strong actionability through concrete scripts and commands, clear workflow sequencing with validation checkpoints, and good progressive disclosure to reference files. The main weakness is some verbosity in the introductory sections explaining what skills are, which could be trimmed given Claude's existing knowledge.
Suggestions
Trim the 'About Skills' and 'What Skills Provide' sections - Claude already understands these concepts; focus on the unique procedural knowledge
Consider moving the 'Core Principles' section to a references file since it's conceptual guidance rather than procedural steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'Think of them as onboarding guides') and could be tightened, but most content is relevant. The 'About Skills' section explains concepts that could be more concise, though the core guidance is valuable. | 2 / 3 |
Actionability | Provides concrete, executable commands (init_skill.py, package_skill.py with exact syntax), specific directory structures, and copy-paste ready examples. The step-by-step process is clear with actual script invocations. | 3 / 3 |
Workflow Clarity | The 6-step skill creation process is clearly sequenced with explicit validation (Step 5 validates before packaging). Each step has clear entry/exit criteria, and the packaging script includes automatic validation with error reporting and retry guidance. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear navigation to references/workflows.md and references/output-patterns.md for advanced patterns. Content is well-organized with appropriate sections, and the skill explicitly teaches progressive disclosure as a design principle. | 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.