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:tibelf/ai_project_init --skill skill-creator79
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/skillEvaluation — 79%
↑ 1.23xAgent success when using this skill
Validation 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 explains its purpose and includes explicit trigger guidance, which is a strength. However, it lacks concrete specific actions that would help Claude understand exactly what this skill teaches, and the trigger terms could be more comprehensive to capture natural user language variations.
Suggestions
Add specific concrete actions like 'write YAML frontmatter', 'define description fields', 'structure skill content sections', or 'set up trigger conditions'
Expand trigger terms to include variations users might naturally say: 'write a skill', 'skill file', 'SKILL.md', 'teach Claude', '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'), with explicit trigger guidance using 'This skill should be used when...' clause. | 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 | Reasonably specific to skill creation, but 'extends Claude's capabilities with specialized knowledge, workflows, or tool integrations' is broad and could overlap with documentation or configuration 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 effectively teaches skill creation. Its main strength is the clear 6-step workflow with concrete examples and executable commands. The primary weakness is some unnecessary conceptual explanation in the opening sections that Claude would already understand, though this doesn't significantly detract from the overall quality.
Suggestions
Trim the 'About Skills' and 'What Skills Provide' sections - Claude understands these concepts; jump directly to 'Core Principles' or merge essential points into a brief intro paragraph.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'Think of them as onboarding guides' metaphor, explaining what skills provide) that Claude would understand implicitly. However, it's mostly efficient with good examples and avoids excessive verbosity in most sections. | 2 / 3 |
Actionability | Provides fully executable commands (init_skill.py, package_skill.py with exact syntax), concrete directory structures, specific YAML frontmatter examples, and copy-paste ready patterns. The step-by-step process is clear and actionable. | 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 based on real usage). | 3 / 3 |
Progressive Disclosure | Excellent structure with clear navigation to external references (references/workflows.md, references/output-patterns.md). Content is well-organized with headers, and the skill appropriately demonstrates the progressive disclosure pattern it teaches. | 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.
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.