CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-developer

Comprehensive guide for creating and managing skills in Claude Code with auto-activation system, following Anthropic's official best practices including the 500-line rule and progressive disclosure pattern.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/skill-developer/SKILL.md

The canonical home for this skill is skill-developer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

Strong actionability and an exemplary step-test-refine workflow with a real checklist, but the document is noticeably self-duplicative (best practices and test commands repeated, plus a padded status footer), and its progressive-disclosure structure is undermined by six referenced reference files that are absent from the bundle.

Suggestions

Delete the duplicated material: fold the 'Quick Reference Summary' and 'Anthropic Best Practices' repeats into their original sections, keep the hook test commands in one place, and remove the 'Skill Status/Line Count/Next' footer.

Ship the six referenced files (TRIGGER_TYPES.md, SKILL_RULES_REFERENCE.md, HOOK_MECHANICS.md, TROUBLESHOOTING.md, PATTERNS_LIBRARY.md, ADVANCED.md) in the bundle — ideally under references/ — or remove the dangling links, since the deep content they promise is currently unreachable.

Convert descriptive sections like 'System Overview' and 'Skill Types' into brief pointers to the (existing) reference files, and add a minimal example of the hook scripts' expected output so the test commands are fully self-contained.

DimensionReasoningScore

Conciseness

The body duplicates its own material several times: the best-practices list appears in Step 1, Step 5, and again as a 7-item 'Anthropic Best Practices' block; the hook test commands appear verbatim in Step 3 and again in 'Troubleshoot'; and the 'Quick Reference Summary' re-summarizes Trigger Types, Enforcement, and Skip Conditions sections already covered in full. Trailing status lines ('Skill Status: COMPLETE ✅', 'Line Count: < 500 ✅', 'Next: ...') are pure padding. This matches 'noticeably verbose; several unnecessary explanations or padded sections'; not 3 because the duplication is systematic rather than incidental, not 1 because there is little explanation of concepts Claude already knows.

2 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste SKILL.md template, a valid skill-rules.json JSON template, runnable test commands ('echo ... | npx tsx .claude/hooks/skill-activation-prompt.ts'), specific env vars (SKIP_SKILL_GUARDRAILS), state-file paths, and a JSON validation command ('jq . skill-rules.json'). Not 5 because sections like 'System Overview' and 'Skill Types' are descriptive rather than instructive, and several code hooks (e.g. skill-verification-guard.ts) are referenced without any example of their content.

4 / 5

Workflow Clarity

The 'Quick Start' gives a clearly sequenced 5-step process with explicit validation (Step 3 test commands, checklist item 'JSON syntax validated: jq . skill-rules.json'), a built-in feedback loop (Step 4: refine patterns based on testing, then retest), and a comprehensive 17-item Testing Checklist for the complex process. This matches the anchor 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'; not 4 because both the checkpoints and the error-recovery loop are explicitly present, not just implied.

5 / 5

Progressive Disclosure

The body is well structured and clearly signals six one-level-deep reference files (TRIGGER_TYPES.md, SKILL_RULES_REFERENCE.md, HOOK_MECHANISMS.md, TROUBLESHOOTING.md, PATTERNS_LIBRARY.md, ADVANCED.md) with per-file content summaries — but none of these files exist in the bundle (no references/ directory and no such files at the skill root), so the promised detailed content is unreachable and the navigation is broken. Not 4/5 because the actual bundle structure fails to deliver the referenced material; not 2 because the SKILL.md itself is genuinely well sectioned and the references are prominently signaled rather than buried.

3 / 5

Total

14

/

20

Passed

Description

61%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 clear, third-person 'what' statement with good domain-specific trigger keywords, but it completely lacks a 'use when' clause, which both limits completeness and weakens its ability to auto-activate on the right prompts. The keyword set also misses several natural terms (SKILL.md, hooks, triggers, frontmatter) that the body itself identifies as central.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or editing skills, modifying skill-rules.json or SKILL.md frontmatter, writing skill trigger patterns, or debugging why a skill does not activate.'

Include the natural terms the body relies on — 'SKILL.md', 'frontmatter', 'hooks', 'skill triggers', 'skill-rules.json' — so users asking about those activate this skill.

Replace generic 'Comprehensive guide for... managing skills' with concrete actions like 'Create skill files, configure trigger rules, and test hook activation' to sharpen specificity.

DimensionReasoningScore

Specificity

The description names its domain ('creating and managing skills in Claude Code with auto-activation system') plus a couple of concrete specifics ('the 500-line rule and progressive disclosure pattern'), but the actions remain generic — creating/managing/following — without covering what the skill actually walks through (hooks, triggers, skill-rules.json). Fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not 4 because it does not list several specific actions, not 2 because the domain and auto-activation specifics go beyond minimal.

3 / 5

Completeness

The 'what' is clearly stated ('Comprehensive guide for creating and managing skills in Claude Code with auto-activation system'), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely missing rather than just under-specified; not 2 because the 'what' is clear and specific.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'creating and managing skills', 'Claude Code', 'auto-activation', 'best practices', '500-line rule', 'progressive disclosure' — phrases a user needing this skill would plausibly say. Not 5 because common variations users actually use — 'SKILL.md', 'frontmatter', 'hooks', 'skill triggers', 'skill-rules.json' — are absent despite being central topics of the skill.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — skill creation/management with auto-activation in Claude Code is a specific meta-task unlikely to collide with domain skills. Not 5 because broad phrases like 'Anthropic's official best practices' and 'progressive disclosure' could overlap with other Claude Code meta/documentation skills; not 3 because the core trigger terms are specific to this niche.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 9 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/skill-developer/SKILL.md

Reviewed

Table of Contents

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.