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

76%

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

77%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 body is a strong, actionable guide with a clear sequenced workflow and executable initialization examples. Its main weaknesses are conceptual padding that hurts conciseness and references to bundled files (workflows.md, output-patterns.md) that do not exist on disk.

Suggestions

Tighten the opening "About Skills" / "What Skills Provide" sections and remove the bridge/field analogy and repeated restatements to reduce conceptual padding and improve token efficiency.

Either create the referenced references/workflows.md and references/output-patterns.md files or remove/inline those pointers so no dead references remain, since no references/ directory exists.

Dimension	Reasoning	Score
Conciseness	At ~384 lines the body is mostly efficient procedural guidance, but includes some conceptual padding Claude already knows (extended "About Skills" framing, the bridge/field analogy, repeated restatements) and could be tightened.	2 / 3
Actionability	Provides a fully executable bash initialization script, concrete YAML frontmatter examples, and worked edit-pdf examples that are copy-paste ready, matching the score-3 anchor despite a couple of abstract pointers.	3 / 3
Workflow Clarity	The Skill Creation Process is an explicit, ordered 5-step sequence with sub-steps, a script-testing validation requirement, and a use-notice-update-retest feedback loop in Step 5; skill creation is not a destructive/batch operation requiring a validate-fix-retry cap.	3 / 3
Progressive Disclosure	The body teaches progressive disclosure well but instructs the reader to consult references/workflows.md and references/output-patterns.md, yet no references/ directory exists — these are dead references, a real navigation defect against the actual (empty) bundle structure.	2 / 3
	Total	10 / 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 conveys both purpose and trigger conditions in third person, with an explicit "should be used when" clause. It is slightly limited on specificity and trigger-term breadth, naming the domain and a few actions rather than a comprehensive list of concrete operations.

Suggestions

Expand the description with more specific concrete actions (e.g., design the SKILL.md frontmatter, bundle scripts/references/assets, set up progressive disclosure) to lift specificity from 2 to 3.

Broaden trigger-term coverage with natural phrasings users might say (e.g., "make a skill", "build a skill", "add a new capability") beyond "create" and "update".

Dimension	Reasoning	Score
Specificity	Names the skill-creation domain and several concrete actions ("create a new skill (or update an existing skill)" with specialized knowledge, workflows, or tool integrations), but stops short of an exhaustive list of specific concrete actions matching the score-3 anchor.	2 / 3
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)...") with explicit trigger guidance.	3 / 3
Trigger Term Quality	Contains natural phrases a user would say ("create a new skill", "update an existing skill") with an explicit "should be used when" clause, but coverage is somewhat narrow and misses common phrasing variations.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (skill creation) with distinct triggers unlikely to overlap with task-performing skills.	3 / 3
	Total	10 / 12 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: 1ca089a

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