skill-creator

Guide for creating effective skills. Use this skill when users need to create a new skill or reshape a draft skill package before hardening, benchmarking, or distribution.

Quality

84%

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

Quality

Content

86%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-structured, concise route-focused skill body with exemplary progressive disclosure and a clear sequenced workflow. The main gap is actionability/workflow_clarity, where validation steps are named abstractly rather than with specific commands and an explicit error-recovery loop.

Suggestions

Name the specific baseline validation command(s) inline in step 5 (e.g. the exact script and expected pass signal) rather than 'Run baseline validation commands'.

Add an explicit validate->fix->retry feedback loop after the validation step so failures are handled before producing the output contract.

Optional: include one short concrete example of a 'changed_files' / 'validation_evidence' entry in the Required output contract to make the output contract copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with no padding and no explanation of concepts Claude already knows; every section (When to use, Core workflow, Required output contract, Constraints) earns its place. It matches the top anchor and is not 4 because there are essentially no trimmable over-explanations.	5 / 5
Actionability	Gives concrete guidance: canonical file names, an explicit output contract field list, and a step to run validation. It is not 5 because 'Run baseline validation commands' names no specific command inline, and not 3 because the guidance is concrete and specific rather than pseudocode-level.	4 / 5
Workflow Clarity	A clear five-step sequenced workflow with a validation/reporting checkpoint in step 5. It is not 5 because there is no explicit validate->fix->retry feedback loop and the validation step is named abstractly, and stays above 3 because the sequence and a checkpoint are clearly present.	4 / 5
Progressive Disclosure	The body is a route-focused overview with well-signaled one-level-deep 'Read when' references to real files (foundations.md, handoff-package-template.md, examples-and-gotchas.md, all present in references/). It matches the top anchor and is not 4 because navigation is explicit and depth is a single level.	5 / 5
	Total	18 / 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 states what the skill does and when to use it with concrete, natural trigger phrases and a clear niche. Its only weak spot is specificity, where the action list is narrow rather than comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating effective skills') and 1-2 concrete actions ('create a new skill', 'reshape a draft skill package') but is not comprehensive in listing specific actions. It does not reach 4 because it lists few discrete actions rather than several, and stays above 2 because the named actions are concrete.	3 / 5
Completeness	Explicitly answers both 'what' (guide for creating/reshaping skills) and 'when' ('Use this skill when users need to create a new skill or reshape a draft skill package') with concrete trigger phrases. It clearly matches the top anchor rather than 4, where 'when' would be less explicit.	5 / 5
Trigger Term Quality	Includes natural user phrasing ('create a new skill', 'reshape a draft skill package') with good coverage of the trigger surface. It is not 5 because it lacks synonyms and broader keyword variations, and stays above 3 because the terms are genuinely natural things a user would say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (skill scaffolding before hardening) with distinct triggers and even scopes out adjacent stages ('before hardening, benchmarking, or distribution'), minimizing conflict risk. It matches the top anchor rather than 4 because the boundaries are explicit, not just mostly distinct.	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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/scaffolding_templates/skill-creator/SKILL.md
Commit: f1f2f21

Reviewed: 2 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.