CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

64%

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-claude/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

67%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 well-structured with executable templates, test commands, and clearly signaled one-level-deep references, but it runs long (~430 lines) with a duplicated summary section and self-promotional footer, and the referenced .md files are not present in the bundle.

Suggestions

Remove the 'Quick Reference Summary' and the trailing 'Skill Status / Next' footer; they restate earlier sections and add no new guidance, trimming ~80 lines.

Either ship the six referenced .md files in a references/ directory or stop citing them; citing nonexistent files undermines progressive disclosure.

Move the detailed Enforcement Levels and Skip Conditions sections into HOOK_MECHANISMS.md so SKILL.md stays a lean overview pointing to detail files.

DimensionReasoningScore

Conciseness

The ~430-line body is mostly structured and useful, but the 'Quick Reference Summary' duplicates Enforcement Levels, Skip Conditions, and Trigger Types already covered above, and the Anthropic Best Practices block repeats in Step 5, the summary, and the self-congratulatory footer ('Skill Status: COMPLETE ✅'). Not a 2 because the padding is repetition rather than explaining concepts Claude already knows; not a 4 because several sections could be trimmed.

3 / 5

Actionability

Provides executable, copy-paste-ready guidance: a frontmatter template, a skill-rules.json snippet, and concrete test commands ('echo ... | npx tsx .claude/hooks/skill-activation-prompt.ts') plus env vars and file markers. Not a 5 because the actual hook implementations are only referenced as file paths, not shown; not a 3 because the common cases are concretely covered.

4 / 5

Workflow Clarity

The 'Quick Start' lays out a clear 5-step sequence (create file, add to skill-rules.json, test, refine, follow best practices) backed by a Testing Checklist with verification items ('jq . skill-rules.json', no false positives/negatives) and a test→refine feedback loop. Not a 5 because some checkpoints are implicit rather than enforced gates; not a 3 because validation/testing steps are explicitly present.

4 / 5

Progressive Disclosure

Six reference files (TRIGGER_TYPES.md, SKILL_RULES_REFERENCE.md, HOOK_MECHANISMS.md, TROUBLESHOOTING.md, PATTERNS_LIBRARY.md, ADVANCED.md) are each clearly signaled with a bullet list of contents and kept one level deep. Not a 5 because none of the referenced files actually exist as bundle files and substantial detail (Enforcement Levels, Skip Conditions, hook architecture) is inlined that overlaps those reference scopes; not a 3 because the navigation and signaling are genuinely good.

4 / 5

Total

15

/

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.

The description clearly conveys the skill's purpose and niche but leans on marketing phrasing ('Comprehensive guide', 'official best practices') and omits any explicit 'Use when...' trigger guidance, capping completeness. Trigger terms are good but could add synonyms and concrete file extensions.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger phrases (e.g., 'Use when creating or adding skills, modifying skill triggers, debugging skill activation, or working with skill-rules.json').

Replace fluff ('Comprehensive guide', 'following Anthropic's official best practices') with a tighter enumeration of concrete actions the skill performs.

Add natural synonyms and concrete file/path triggers (e.g., '.claude/skills/', 'SKILL.md', 'hooks') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ('creating and managing skills in Claude Code with auto-activation system') but pads with fluff ('Comprehensive guide', 'following Anthropic's official best practices') and does not enumerate a comprehensive action list. Not a 2 because two real actions are named; not a 4 because the actions are generic rather than a list of several specific ones.

3 / 5

Completeness

Clearly states what the skill does ('guide for creating and managing skills... with auto-activation system') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric. Not a 4 because the 'when' is only weakly implied; not a 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('creating and managing skills in Claude Code', 'auto-activation', '500-line rule', 'progressive disclosure') with good coverage of the skill-development niche. Not a 5 because synonyms and file-extension variants are missing; not a 3 because the term set is broader than a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Claude Code skill creation/management with auto-activation) with mostly distinct triggers and minor overlap risk only with general 'Claude Code best practices' skills. Not a 5 because 'Claude Code best practices' is broad enough to invite some overlap; not a 3 because the core triggers are specific to skill development.

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.

Validation14 / 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
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.