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

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 ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/scaffolding_templates/skill-creator/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

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 concise, well-organized, and demonstrates strong progressive disclosure with verified references and a validation checkpoint in its workflow. Its main weakness is actionability, where guidance stays at a descriptive level rather than specifying concrete file templates or commands.

Suggestions

Add concrete inline specifics for the actionability gap, e.g. name the canonical required files (SKILL.md, references/, scripts/, agents/openai.yaml) and the exact baseline validation command(s) to run in step 5.

Provide a minimal inline template or example of a handoff payload matching the 'Required output contract' fields so Claude can produce it directly.

Tighten the 'Core workflow' steps by linking each to the relevant reference (e.g. step 4 -> progressive disclosure policy) so the route is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and route-focused with no explanation of concepts Claude already knows; every section (workflow, output contract, anti-patterns, constraints) earns its place, matching anchor 3.	3 / 3
Actionability	Guidance is moderately concrete but largely describes ('Create/update required files with canonical names,' 'Move deep details to references') rather than providing specific file templates or commands inline; matches anchor 2 and is not 3 because key details are left unspecified.	2 / 3
Workflow Clarity	A clear 5-step numbered sequence includes an explicit validation checkpoint (step 5: 'Run baseline validation commands and report outcomes'); since the task involves no destructive or batch operations, it is not capped at 2, matching anchor 3.	3 / 3
Progressive Disclosure	The body is a clear overview with three well-signaled, one-level-deep references (foundations, handoff-package-template, examples-and-gotchas), all verified to exist, with content appropriately split; matches anchor 3.	3 / 3
	Total	11 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 clearly states both what the skill does and when to use it, with an explicit trigger clause and a distinct niche. It is slightly held back by process-level rather than concretely enumerated actions and incomplete coverage of natural trigger phrasings.

Dimension	Reasoning	Score
Specificity	Names the skill-creation domain and several actions ('creating,' 'reshape a draft skill package,' 'before hardening, benchmarking, or distribution'), but the actions are process-level rather than a comprehensive list of concrete operations, matching anchor 2; not 3 because it lacks multiple specific concrete actions.	2 / 3
Completeness	Explicitly answers both what ('Guide for creating effective skills') and when ('Use this skill when users need to create a new skill or reshape a draft skill package'), matching anchor 3 with an explicit 'Use this skill when...' trigger clause.	3 / 3
Trigger Term Quality	Includes relevant natural terms a user might say ('create a new skill,' 'reshape a draft skill package') but misses common variations like 'build' or 'set up a skill,' matching anchor 2; not 3 due to incomplete coverage of natural phrasings.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (pre-hardening skill creation/reshape) with distinct triggers and explicit routing away from sibling skills in the body, making conflict unlikely; matches anchor 3.	3 / 3
	Total	10 / 12 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: 46e4be2

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