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.

1.25x

Quality

46%

Does it follow best practices?

Impact

79%

1.25x

Average score across 7 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-creator/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive guide for creating skills but suffers from significant verbosity—it explains many concepts Claude already understands (what skills are, what scripts/references/assets mean) and includes lengthy illustrative examples inline that could live in reference files. The workflow is reasonably clear with a 6-step process, but the skill would benefit greatly from practicing the conciseness and progressive disclosure principles it preaches.

Suggestions

Reduce the 'About Skills' and 'What Skills Provide' sections to 2-3 sentences max—Claude already understands modular knowledge packages; focus only on the structural requirements (SKILL.md + optional bundles).

Move the detailed progressive disclosure patterns and examples (Pattern 1, 2, 3) into a reference file like references/progressive-disclosure-examples.md, keeping only a brief summary and link in SKILL.md.

Add a concrete end-to-end example of a minimal but complete SKILL.md (frontmatter + body) to make Step 4's 'Write instructions' guidance actionable rather than abstract.

Add explicit validation checkpoints in Step 4 (e.g., 'After writing SKILL.md, verify it is under 500 lines and all referenced bundle files exist') rather than deferring all validation to Step 5's packaging script.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines, with significant portions explaining concepts Claude already knows (what skills are, what PDFs are, what scripts/references/assets mean conceptually). Sections like 'What Skills Provide' and 'About Skills' are largely unnecessary preamble. Many paragraphs could be condensed to single sentences or bullet points.	1 / 3
Actionability	The skill provides concrete commands for init_skill.py and package_skill.py with usage examples, and includes specific directory structures. However, much of the guidance remains abstract (e.g., 'Write instructions for using the skill' in Step 4 Body section is vague), and there are no concrete examples of what a good SKILL.md body actually looks like end-to-end.	2 / 3
Workflow Clarity	The 6-step creation process is clearly sequenced and well-labeled, with skip conditions noted. However, validation is only mentioned at the packaging step (Step 5) and there are no explicit feedback loops for intermediate steps like testing scripts in Step 4. The instruction to test scripts is mentioned but lacks a concrete validation checkpoint pattern.	2 / 3
Progressive Disclosure	The skill references external files (references/workflows.md, references/output-patterns.md) with clear descriptions of when to consult them, which is good. However, the SKILL.md itself is monolithic and contains extensive inline content (e.g., the entire 'Core Principles' section, detailed progressive disclosure patterns with examples) that could be split into reference files. The skill teaches progressive disclosure but doesn't fully practice it.	2 / 3
	Total	7 / 12 Passed

Description

57%

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 has good completeness with an explicit 'when to use' clause covering both creation and updating of skills. However, it lacks specificity about what concrete actions the skill performs (e.g., generating frontmatter, structuring markdown, defining triggers). The trigger terms are adequate but could be expanded with more natural variations users might employ.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Guides creation of SKILL.md files including YAML frontmatter, description fields, and markdown instruction blocks'

Expand trigger terms to include natural variations like 'SKILL.md', 'skill file', 'teach Claude how to', 'custom workflow', or 'skill template'

Dimension	Reasoning	Score
Specificity	The description says 'creating effective skills' and 'extends Claude's capabilities with specialized knowledge, workflows, or tool integrations' but these are vague and abstract. No concrete actions like 'generates YAML frontmatter', 'writes markdown instructions', or 'validates skill structure' are mentioned.	1 / 3
Completeness	The description answers both 'what' (guide for creating effective skills that extend Claude's capabilities) and 'when' ('should be used when users want to create a new skill or update an existing skill'). The 'Use when' clause is explicit with clear triggers.	3 / 3
Trigger Term Quality	Includes some relevant trigger terms like 'create a new skill', 'update an existing skill', and 'skill' itself. However, it misses natural variations users might say such as 'SKILL.md', 'skill file', 'teach Claude', 'custom instruction', or 'skill template'.	2 / 3
Distinctiveness Conflict Risk	The skill is somewhat distinctive in targeting skill creation specifically, but the vague language about 'specialized knowledge, workflows, or tool integrations' could overlap with general documentation or configuration skills. The term 'skill' as a trigger is fairly specific to this domain though.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: tibelf/ai_project_init
Commit: 56f4516

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.