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

65%

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 ./bundled/skills/skill-creator/SKILL.md

Quality

Content

67%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 skill body is a well-structured, actionable meta-skill: it sequences a clear creation workflow with validation, and properly uses one-level-deep reference files that genuinely exist. Its main weakness is conciseness — several analogies and re-explanations of principles Claude already grasps add tokens without proportional value.

Suggestions

Trim explanatory padding Claude does not need, e.g. the "onboarding guides" analogy in About Skills and the bridge/cliff metaphor under Set Appropriate Degrees of Freedom, keeping only the actionable guidance.

Replace the "[code example]" placeholder inside the Pattern 1 illustration with a minimal real snippet so every code block is genuinely executable.

Consider moving the three multi-line Pattern illustrations (high-level guide, domain organization, conditional details) into a reference file, since they duplicate guidance already conveyed by the prose, reducing SKILL.md length.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but contains some explanatory padding Claude does not need (e.g. "Think of them as 'onboarding guides'", the bridge/cliff metaphor for degrees of freedom, and restating that the context window is a shared good after the frontmatter already implies it), matching the anchor for mostly efficient content with some unnecessary explanation that could be tightened.	3 / 5
Actionability	It gives concrete executable commands (init_skill.py, package_skill.py invocations with arguments and output-dir variants) and points to real reference files for patterns, with only minor gaps (the "[code example]" placeholder inside the Pattern 1 illustration is illustrative, not a runnable snippet), fitting the mostly-executable anchor.	4 / 5
Workflow Clarity	The six-step creation process is clearly sequenced with explicit ordering guidance ("Follow these steps in order, skipping only if..."), per-step validation cues (test scripts before packaging, packaging auto-validates), and an iteration feedback loop; the minor gap is that step-level validation checkpoints within step 4 are described rather than numbered, landing just below the score-5 anchor.	4 / 5
Progressive Disclosure	SKILL.md is organized into clear sections and correctly offloads detailed patterns to one-level-deep reference files (references/workflows.md, references/output-patterns.md) that are real bundle files and clearly signaled with when-to-read guidance; the minor gap is that several long inline illustrations (anatomy tree, three Pattern markdown blocks) could themselves be trimmed or moved, keeping it just below the score-5 anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly answers both what the skill does and when to use it in third person, with a clear niche and low conflict risk. Its weaknesses are moderate specificity (only a few concrete capabilities listed) and trigger-term coverage that misses natural synonyms like "build" or "write" a skill.

Suggestions

Replace the generic verb "Guide for creating" with several concrete actions, e.g. "Create, update, and package skills that bundle scripts, references, and assets."

Broaden trigger terms to include natural phrasings users say, such as "build a skill", "write a skill", "make a skill", or "skill authoring".

Tighten the "when" clause with explicit trigger contexts, e.g. "Use when the user asks to create, update, package, or validate a Claude skill."

Dimension	Reasoning	Score
Specificity	Names the domain (creating/updating skills) and a couple concrete facets ("specialized knowledge, workflows, or tool integrations"), but the actions remain general ("Guide for creating") rather than enumerating several specific concrete operations, matching the score-3 anchor of domain plus 1-2 actions that are not comprehensive.	3 / 5
Completeness	It states both what ("Guide for creating effective skills... extends Claude's capabilities with specialized knowledge, workflows, or tool integrations") and when ("This skill should be used when users want to create a new skill (or update an existing skill)"), but the trigger phrasing is somewhat general rather than packed with concrete trigger phrases, fitting the anchor where both what and when are present but when could be more explicit.	4 / 5
Trigger Term Quality	It includes relevant natural phrases ("create a new skill", "update an existing skill") but omits common variations users would say (e.g. "build a skill", "write a skill", "skill") and has no synonym or file-extension coverage, matching the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	It occupies a fairly clear niche (skill authoring) with a distinct trigger ("create a new skill (or update an existing skill)") that is unlikely to fire for unrelated skills, with only minor overlap risk against generic authoring/editing skills, matching the mostly-distinct anchor.	4 / 5
	Total	14 / 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/skill-creator/SKILL.md
Commit: d5ae560

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.