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:daymade/claude-code-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
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 communicates its purpose and includes explicit 'when to use' guidance, which is a strength. However, it lacks specific concrete actions (what exactly does creating a skill involve?) and could benefit from more natural trigger terms users might actually say. The scope description ('specialized knowledge, workflows, or tool integrations') is somewhat generic.
Suggestions
Add specific concrete actions like 'write YAML frontmatter, define trigger conditions, structure skill markdown content, add examples'
Include more natural trigger term variations such as 'skill file', 'skill template', 'extend Claude', 'teach Claude', or 'custom 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') with explicit trigger guidance. | 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', '.md skill', or 'skill template'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to skill creation, but 'specialized knowledge, workflows, or tool integrations' is broad and could overlap with other meta-skills or documentation skills. The term 'skill' is distinctive but the scope description is vague. | 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-crafted meta-skill for creating skills, with excellent workflow clarity and actionability. The step-by-step process is comprehensive with proper validation checkpoints and clear commands. The main weakness is some verbosity in the introductory sections that could be trimmed without losing clarity.
Suggestions
Trim the 'About Skills' section - Claude already understands what skills are; focus on the unique aspects of this skill system rather than general explanations
Consider moving the 'Anatomy of a Skill' detailed breakdown to a references file, keeping only a brief summary in SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'Think of them as onboarding guides') and could be tightened in places, but overall provides useful information without excessive padding. The 'About Skills' section explains concepts that could be more concise. | 2 / 3 |
Actionability | Provides concrete, executable commands throughout (init_skill.py, package_skill.py, security_scan.py, grep patterns), specific file structures, and copy-paste ready examples. The step-by-step process is highly actionable with real commands. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-9), explicit validation checkpoints (Step 6 security review, Step 7 packaging validation), and feedback loops (Step 9 iteration). Each step has clear entry/exit criteria and skip conditions. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of external references (references/sanitization_checklist.md, external Anthropic docs link), and content appropriately organized. The skill overview stays lean while pointing to detailed resources. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 14 / 16 Passed | |
- 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.