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.

1.25x

Quality

76%

Does it follow best practices?

Impact

79%

1.25x

Average score across 7 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/skill-creator/SKILL.md

Quality

Content

71%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 is a well-organized, largely actionable guide with clear sequencing, a real validation feedback loop, and excellent progressive disclosure via real referenced files. Its main weakness is conciseness — it opens by explaining skill fundamentals Claude likely already knows.

Suggestions

Trim the 'About Skills' introduction and 'What Skills Provide' list; assume Claude knows what skills are and keep only the non-obvious design philosophy.

Add an explicit validation/checkpoint step earlier in the workflow (e.g., after Step 4 editing) rather than concentrating all validation in the packaging step.

Tighten prose passages like the 'context window is a public good' paragraph to imperative guidance without the explanatory preamble.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured, but the opening ('Skills are modular, self-contained packages... Think of them as onboarding guides...') and several prose passages explain concepts Claude already knows. Not a 4 because the padded conceptual exposition is noticeable; not a 2 because the bulk is genuinely useful procedural guidance rather than pervasive padding.	3 / 5
Actionability	Provides concrete executable commands (scripts/init_skill.py, scripts/package_skill.py — both real files) and worked examples for scripts/references/assets. Not a 5 because the 'Edit the Skill' step relies on guidance rather than copy-paste-ready code; not a 3 because the init/package steps are fully executable.	4 / 5
Workflow Clarity	A clear 6-step sequence with an explicit validate-then-fix-then-rerun feedback loop in the packaging step ('If validation fails... Fix any validation errors and run the packaging command again'). Not a 5 because validation/checkpoints are concentrated at packaging rather than woven through each step; not a 3 because a real feedback loop is present.	4 / 5
Progressive Disclosure	Body is ~350 lines (under the 500-line guidance) with design-pattern detail split into clearly signaled, one-level-deep references (references/workflows.md, references/output-patterns.md) and real scripts, all referenced from SKILL.md. Matches the anchor-5 pattern of a concise overview pointing to well-signaled separate files.	5 / 5
	Total	16 / 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 clearly states what the skill does and gives explicit, natural trigger guidance for when to use it, with a distinct niche that minimizes conflict risk. The only weakness is moderate action specificity and slightly limited trigger-term variety.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating effective skills') and 1-2 concrete actions ('create a new skill', 'update an existing skill'), but the action list is not comprehensive. Not a 2 because the actions are clearly stated rather than minimal/generic; not a 4 because only create/update are named with no further specific actions.	3 / 5
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 concrete trigger phrases. Meets the anchor-5 example; the explicit 'Use when'-style clause avoids the cap at 3.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('create a new skill', 'update an existing skill') with good coverage. Not a 5 because synonyms like 'build'/'make a skill' and explicit file extensions are missing; not a 3 because more than one natural trigger phrase is present and they are well-targeted.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (skill authoring) with distinct triggers unlikely to fire for unrelated skills. Not a 4 because there is no meaningful overlap with closely related skills — 'creating skills' is a distinct, narrow intent.	5 / 5
	Total	17 / 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: Project-N-E-K-O/N.E.K.O
Path: .agent/skills/skill-creator/SKILL.md
Commit: e1fa348

Reviewed: ~22 hours 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.