skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Install with Tessl CLI
npx tessl i github:chrisboden/cursor-skills --skill skill-creatorOverall
score
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/skillValidation for skill structure
Discovery
75%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 communicates its purpose and includes explicit 'when to use' guidance, which is a strength. However, it lacks specific concrete actions that would help Claude understand the full scope of what this skill enables, and could benefit from more natural trigger term variations that users might actually say.
Suggestions
Add specific concrete actions like 'write YAML frontmatter, define trigger conditions, structure skill markdown content, add usage examples'
Include more natural trigger term variations such as 'SKILL.md', 'write a skill', 'skill file', 'teach Claude', or 'new capability'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (creating skills) and mentions some actions ('create a new skill', 'update an existing skill'), but lacks concrete specific actions like 'write YAML frontmatter', 'define trigger conditions', or 'structure skill content'. | 2 / 3 |
Completeness | Clearly answers both what ('Guide for creating effective skills') and when ('when users want to create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'skill', 'create', 'update', but misses common variations users might say such as 'write a skill', 'new capability', 'skill file', 'SKILL.md', or 'extend Claude'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on skill creation/modification, with distinct triggers around 'skill' and 'extends Claude's capabilities' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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, actionable skill with clear workflows and validation checkpoints. Its main weakness is verbosity—the 'About Skills' section explains concepts Claude already understands, and detailed resource documentation could be moved to reference files. The actionable process steps (3-6) are excellent and provide concrete, executable guidance.
Suggestions
Move the 'About Skills' conceptual explanation to a references/skill-anatomy.md file and keep only a brief summary in SKILL.md
Condense the 'What Skills Provide' and 'Anatomy of a Skill' sections—Claude understands these concepts and needs only the specific structural requirements
Consider moving the detailed scripts/references/assets documentation to a separate reference file, keeping only essential guidance in SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., explaining what skills are to Claude, the 'About Skills' section with conceptual framing). While mostly efficient, sections like 'What Skills Provide' and 'Anatomy of a Skill' explain concepts that could be more condensed. | 2 / 3 |
Actionability | Provides concrete, executable commands (init_skill.py, package_skill.py with exact usage), specific file structures, and clear examples of how to analyze use cases. The step-by-step process is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential process with explicit validation built into Step 5 (packaging validates before creating). Each step has clear entry/exit criteria and the iteration loop in Step 6 provides feedback recovery. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic—detailed information about scripts/, references/, and assets/ could be split into separate reference files. The 'About Skills' section adds significant length that could be externalized. | 2 / 3 |
Total | 10 / 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.