Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
81
Quality
76%
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 ./openclaw/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 adequately covers the what and when aspects with explicit trigger guidance, 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, validate skill structure'
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'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'skills', 'scripts', 'references', 'assets', but misses common variations users might say such as '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, highly actionable skill that provides clear workflows for creating skills. Its main weakness is some verbosity in the introductory sections explaining concepts Claude likely already understands (what skills are, why conciseness matters). The progressive disclosure and workflow clarity are excellent, with concrete scripts and clear step-by-step processes.
Suggestions
Remove or significantly condense the 'About Skills' and 'What Skills Provide' sections - Claude doesn't need to be told what skills are or why they're useful
Trim the 'Core Principles' section to focus only on non-obvious guidance; the explanation of why conciseness matters is itself not concise
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., explaining what skills are to Claude, the 'About Skills' section) and could be tightened. However, it does provide valuable procedural knowledge and avoids excessive verbosity in most sections. | 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 clearly actionable with real script invocations. | 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 (Step 6: Iterate). | 3 / 3 |
Progressive Disclosure | Excellent structure with clear navigation to reference files (references/workflows.md, references/output-patterns.md). Content is well-organized with appropriate sections, and references are one level deep with clear signaling for when to consult them. | 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.
8763418
Table of Contents
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.