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

78%

Does it follow best practices?

Impact

79%

1.25x

Average score across 7 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

73%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.

A well-structured, largely actionable guide whose strongest points are the explicit validate-fix-retry packaging loop and correctly-signaled, real one-level-deep references. Its main weakness is token efficiency: analogies, per-resource benefit bullet lists, and conceptual pattern walkthroughs pad the body and partially duplicate what could live in references/.

Suggestions

Trim conciseness: cut the bridge/cliffs analogy and collapse the repeated "When to include / Examples / Benefits / Use cases" bullet lists for scripts, references, and assets into a single compact table.

Move the three progressive-disclosure pattern walkthroughs (Patterns 1-3) into a references/patterns.md file and keep only the selection principle inline in SKILL.md, following the skill's own "Key principle" guidance.

Replace the "[code example]" placeholder in Pattern 1 with a real snippet or delete the placeholder line so every example in the body is concrete.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, non-obvious procedural guidance, but includes padded sections: the "narrow bridge with cliffs" analogy, repeated "When to include / Examples / Benefits" bullet lists for each resource type, and an "About Skills" meta-explanation that restates what skills are. It could be tightened without losing substance.	3 / 5
Actionability	Provides executable commands ("scripts/init_skill.py <skill-name> --path <output-directory>", "scripts/package_skill.py <path/to/skill-folder> ./dist"), a concrete model description for the docx skill, and specific example questions to ask users. Minor gaps: the "[code example]" placeholders in Pattern 1 are illustrative pseudocode rather than real content.	4 / 5
Workflow Clarity	The six-step creation process is clearly sequenced with explicit skip conditions per step, and includes a validation feedback loop: the packaging script "automatically validates the skill first", and "If validation fails, the script will report the errors and exit... Fix any validation errors and run the packaging command again". Added scripts "must be tested by actually running them".	5 / 5
Progressive Disclosure	The body (~357 lines) stays under its own 500-line limit and links one-level-deep references that exist in the bundle ("See references/workflows.md for sequential workflows", "See references/output-patterns.md for template and example patterns") plus scripts/init_skill.py and scripts/package_skill.py. However, conceptual material such as the three progressive-disclosure patterns and the degrees-of-freedom discussion is inlined in SKILL.md when it could itself be split into a reference file.	4 / 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.

A strong description: third-person, explicit what-and-when with natural trigger phrases and a distinct niche. Its only weakness is that the capability statement is somewhat generic ("Guide for creating effective skills") and misses common synonyms like "build" or "author" a skill.

Dimension	Reasoning	Score
Specificity	Names the domain ("creating effective skills") and 1-2 concrete actions ("create a new skill", "update an existing skill"), but "Guide for creating effective skills" is generic and no broader action list is given. Not 4: it does not list several specific actions the way the higher anchor requires.	3 / 5
Completeness	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)"), in third person, with a concrete trigger phrase. Not 4: the when clause is explicit and specific, not merely present-but-vague.	5 / 5
Trigger Term Quality	Includes natural phrases users would actually say ("create a new skill", "update an existing skill") rather than jargon. Not 5: common synonyms such as "build a skill", "make a skill", or "skill authoring" are missing.	4 / 5
Distinctiveness Conflict Risk	Skill creation is a clear niche with distinct triggers ("create/update a skill... that extends Claude's capabilities"); it would not plausibly fire for an unrelated skill.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 missing	Warning
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: mixpanel/mixpanel-headless
Path: .claude/skills/skill-creator/SKILL.md
Commit: aa4e414

Reviewed: 1 day 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.