Skills

Skill Developer

Create and manage Claude Code skills following Anthropic best practices.

Install

npx skills add diet103/claude-code-infrastructure-showcase --skill skill-developer -g -a claude-code -y
Category
Testing
Updated
4mo ago
License
MIT
Context cost
Mediumabout 3,000 tokens
Runs scripts
No, instructions only

What it does

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.

Skill Developer Guide

Purpose

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.

When to Use This Skill

Automatically activates when you mention:

  • Creating or adding skills
  • Modifying skill triggers or rules
  • Understanding how skill activation works
  • Debugging skill activation issues
  • Working with skill-rules.json
  • Hook system mechanics
  • Claude Code best practices
  • Progressive disclosure
  • YAML frontmatter
  • 500-line rule

System Overview

Hook Architecture (five wired hooks)

1. UserPromptSubmit Hook (Proactive Suggestions)

  • File: .claude/hooks/skill-activation-prompt.ts
  • Trigger: BEFORE Claude sees user's prompt
  • Purpose: Suggest relevant skills based on keywords + intent patterns (regex or optional AI classification)
  • Method: Injects formatted reminder as context (stdout → Claude's input)
  • Enforcement: Only enforcement: "block" skills are marked MANDATORY; suggest/warn skills always appear as recommendations

2. PreToolUse Hook - Skill Verification Guard (Enforcement)

  • File: .claude/hooks/skill-verification-guard.ts
  • Trigger: BEFORE Edit/MultiEdit/Write executes
  • Purpose: Enforce mandatory skill activation (two-try model) and guardrail file/content patterns; optional AI edit analysis
  • Method: Exit code 2 + stderr blocks the tool; only enforcement: "block" skills can block

3. PostToolUse Hook - Edit Tracker

  • File: .claude/hooks/post-tool-use-tracker.sh
  • Trigger: AFTER Edit/MultiEdit/Write completes
  • Purpose: Track edited files and repos (feeds build checks and the error-handling reminder)
Read the whole SKILL.md on GitHub

More in Testing