create-skill

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 your capabilities with specialized knowledge, workflows, or tool integrations.

Quality

66%

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 ./crates/forge_repo/src/skills/create-skill/SKILL.md

Quality

Content

63%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 body offers concrete, well-sequenced guidance for skill creation with executable examples and a clear iterative workflow. It is held back by conceptual padding, a monolithic structure, and two broken references to missing bundle files.

Suggestions

Trim conceptual padding (the onboarding-guide and narrow-bridge metaphors, repeated context-window explanations) to practice the conciseness the skill preaches.

Create the referenced references/workflows.md and references/output-patterns.md, or remove the broken "See references/..." links in Step 4.

Gate the script-testing step explicitly (e.g., "only proceed when scripts run and output matches expectations") to strengthen validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful procedural content but includes unnecessary padding Claude already knows (the "onboarding guides" metaphor, repeated "context window is a public good" explanations, the "narrow bridge with cliffs" metaphor), so it could be tightened rather than being lean.	3 / 5
Actionability	It provides mostly executable guidance including a copy-paste-ready bash init script, concrete naming conventions, and a clear 5-step process with specific user questions, with only minor gaps (TODO placeholders, references to non-existent files).	4 / 5
Workflow Clarity	The 5-step creation process is clearly sequenced with an explicit test-scripts checkpoint and an iteration feedback loop (Step 5), but validation is not tightly gated (no "only proceed when tests pass"), leaving minor validation gaps short of a 5.	4 / 5
Progressive Disclosure	The body has clear section structure but is monolithic (~385 lines with everything inline) and its two real cross-file references (references/workflows.md, references/output-patterns.md) point to files that do not exist, a navigation gap worse than minor.	3 / 5
	Total	14 / 20 Passed

Description

68%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 clearly communicates a distinct niche (skill creation) with an explicit, natural trigger phrase for when to use it. Its main weaknesses are a slightly generic "what" statement and second-person voice ("your capabilities") that costs it specificity.

Suggestions

Rewrite in third person to avoid "extends your capabilities"; e.g., "Guides creation of skills that extend agent capabilities...".

Make the "what" more concrete by enumerating the key actions (e.g., plan reusable resources, write SKILL.md frontmatter, bundle scripts/references/assets).

Add common trigger synonyms like "build" or "make a skill" to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and two concrete actions ("create a new skill (or update an existing skill)"), matching anchor 3, but is reduced by 1 for second-person voice ("extends your capabilities"), landing at 2.	2 / 5
Completeness	It explicitly answers both what ("Guide for creating effective skills") and when ("when users want to create a new skill (or update an existing skill)") with a concrete trigger phrase, but the "what" is somewhat generic rather than enumerating concrete capabilities, keeping it just below a 5.	4 / 5
Trigger Term Quality	It includes natural trigger phrases users would actually say ("create a new skill", "update an existing skill") with good coverage, but misses common synonyms like "build" or "make a skill", so it is not comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	Skill creation is a clear, distinct meta-skill niche with a specific trigger (create/update a skill) and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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: 14 missing	Warning

	Total	14 / 16 Passed

Repository: tailcallhq/forgecode
Path: crates/forge_repo/src/skills/create-skill/SKILL.md
Commit: 6ed5d37

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