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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

77%Weight 40%Scale 1-5

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

The content is a well-sequenced, actionable meta-skill with a strong validation feedback loop in its packaging step. Its main weaknesses are mild over-explanation of familiar concepts and a progressive-disclosure gap: it references a missing package_skill.py and ships no reference files while inlining reference-style material.

Suggestions

Provide the missing scripts/package_skill.py referenced in Step 5, or correct the reference to the actual available script (e.g., quick_validate.py), so bundle references are real.

Trim onboarding-style explanation of what skills are (lines 13-16, 77-85) since Claude already knows this, keeping only the non-obvious structural guidance.

Move detailed reference material (resource-type guidance and examples) into a references/ file and link to it from SKILL.md to better realize the described three-level loading model.

Dimension	Reasoning	Score
Conciseness	The body is efficiently organized into clear sections with concrete commands and examples, but includes some mild over-explanation of concepts Claude already knows (e.g., 'Skills are modular, self-contained packages... Think of them as onboarding guides') that could be trimmed.	4 / 5
Actionability	It provides concrete, executable guidance such as the init_skill.py invocation and packaging commands plus worked examples (pdf-editor, frontend-webapp-builder, big-query), with a minor gap: the referenced scripts/package_skill.py does not exist in the bundle.	4 / 5
Workflow Clarity	The six-step process is explicitly sequenced ('follow in order, skipping steps only if there is a clear reason') and Step 5 includes an explicit validation feedback loop ('If validation fails... fix any validation errors and run the packaging command again'), matching the anchor for clear sequence with validation and error recovery.	5 / 5
Progressive Disclosure	The body has good section structure and explains a three-level loading system, but it inlines reference-style material, ships no references/ files, and references a bundled script (package_skill.py) that is not present in the bundle, leaving references not clearly signaled against the actual file listing.	3 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

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 is strong: it clearly states both what the skill does and when to use it in third person, with a distinct niche and minimal conflict risk. Its only weakness is moderate specificity and trigger-term breadth, where synonyms and variations would improve coverage.

Suggestions

Add concrete actions the skill performs (e.g., 'scaffold, validate, and package skills') to lift specificity toward comprehensive coverage.

Include natural trigger synonyms users might say, such as 'build a skill', 'scaffold a skill', or 'package a skill for distribution', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('creating effective skills') and concrete facets ('specialized knowledge, workflows, or tool integrations'), matching the anchor for naming the domain plus 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It explicitly answers both what ('Guide for creating effective skills') and when ('This skill should be used when users want to create a new skill (or update an existing skill)') with a concrete trigger phrase, in third person.	5 / 5
Trigger Term Quality	It includes a natural user phrasing ('when users want to create a new skill (or update an existing skill)') with good keyword coverage, but lacks common synonyms like 'build a skill' or skill-file extensions; a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The meta-skill niche of skill creation is clearly distinct with trigger phrases unlikely to collide with other skills, presenting minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 14 missing	Warning

	Total	15 / 16 Passed

Repository: Raudbjorn/claude
Path: skill-creator/SKILL.md
Commit: bd02b72

Reviewed: 4 days 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.