skill-creator
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 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, comprehensive skill that provides actionable guidance for creating skills. Its main strength is the clear 6-step workflow with concrete commands and validation checkpoints. The content could be more concise in places—some explanatory sections (like 'About Skills' and 'What Skills Provide') add tokens without proportional value for an AI reader.
Suggestions
Trim the 'About Skills' and 'What Skills Provide' sections significantly—Claude understands what modular packages and domain expertise are; focus on the specific conventions unique to this skill system.
Consider moving the detailed 'Progressive Disclosure Design Principle' patterns to a reference file, keeping only a brief summary in SKILL.md with a pointer to the detailed examples.
| 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 procedural knowledge that Claude wouldn't inherently know about skill creation conventions. | 2 / 3 |
Actionability | Provides concrete, executable commands (init_skill.py, package_skill.py with full usage examples), specific directory structures, and copy-paste ready code patterns throughout. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential process with explicit validation built into Step 5 (packaging validates automatically), and the workflow includes feedback loops in Step 6 for iteration based on real usage. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section hierarchy, references to external files (references/workflows.md, references/output-patterns.md) are one level deep and clearly signaled with specific use cases 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.
- Repository
- trpc-group/trpc-agent-go
- Commit
50ef2f3
- 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.