skill-developer

Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.

Quality

71%

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 ./.claude/skills/skill-developer/SKILL.md

Quality

Content

56%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 actionable and reasonably well-sequenced, but it is padded with redundant summary sections and dangling references to missing files, hurting token efficiency and the progressive-disclosure promise.

Suggestions

Remove the 'Quick Reference Summary' section (and other restated Enforcement/Skip/Best-Practices blocks) since they duplicate content already covered above; link to reference files instead.

Create the six referenced files (TRIGGER_TYPES.md, SKILL_RULES_REFERENCE.md, HOOK_MECHANISMS.md, TROUBLESHOOTING.md, PATTERNS_LIBRARY.md, ADVANCED.md) or drop the links so progressive disclosure is fulfilled rather than promised.

Move the '2025-10-27' philosophy-change note into a deprecated/old-patterns section so the time-sensitive date does not penalize conciseness over time.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose with redundant sections — the 'Quick Reference Summary' repeats Quick Start, Enforcement Levels, Skip Conditions, and Anthropic Best Practices — plus emoji decoration and a time-sensitive 'Philosophy Change (2025-10-27)' date that will age.	2 / 5
Actionability	Provides concrete, mostly copy-paste-ready guidance: npx tsx test commands, a skill-rules.json template, bash env exports, and a file-marker example, with only minor gaps.	4 / 5
Workflow Clarity	The 5-step Quick Start is clearly sequenced with a Test→Refine feedback loop and a thorough Testing Checklist; validation is present though some checkpoints are implicit rather than enforced.	4 / 5
Progressive Disclosure	Six reference files are clearly signaled one-level-deep with content descriptions, but none of the referenced bundle files actually exist, and some detail (enforcement levels, skip conditions) is duplicated inline rather than split out.	3 / 5
	Total	13 / 20 Passed

Description

87%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.

A strong description that clearly states purpose and triggers with concrete, natural language and a distinct niche. Slightly limited actionverb diversity and synonym coverage keep specificity and trigger_term_quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Enumerates comprehensive coverage (trigger types, enforcement levels, hook mechanisms, session tracking, 500-line rule) but the action verbs are limited to 'create and manage', leaving minor gaps versus the fully comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('Create and manage Claude Code skills following Anthropic best practices') and when ('Use when creating new skills, modifying skill-rules.json, ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('creating new skills', 'modifying skill-rules.json', 'debugging skill activation') plus a filename, but lacks common synonyms and variations for a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Claude Code skill authoring) with distinct triggers like skill-rules.json, hook mechanisms, and skill activation, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 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
relative_links	Relative link issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: diet103/claude-code-infrastructure-showcase
Path: .claude/skills/skill-developer/SKILL.md
Commit: 07f75ce

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