skill developer

AI Community

Skill notes

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

Two-Hook Architecture

  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 Method: Injects formatted reminder as context (stdout → Claude's input)

Configuration File

Location: .claude/skills/skill-rules.json Defines: All skills and their trigger conditions Enforcement levels (block, suggest, warn) File path patterns (glob)

1. Guardrail Skills

Purpose: Enforce critical best practices that prevent errors Characteristics: Type: "guardrail" Enforcement: "block" Priority: "critical" or "high"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Microck · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Create Skill File

Location: `.claude/skills/{skill-name}/SKILL.md` Template: Best Practices: ✅ Name: Lowercase, hyphens, gerund form (verb + -ing) preferred ✅ Description: Include ALL trigger keywords/phrases (max 1024 chars)

02
Step 2: Add to skill-rules.json

See SKILL_RULES_REFERENCE.md for complete schema. Basic Template:

03
Step 3: Test Triggers

Test UserPromptSubmit: Test PreToolUse:

04
Step 4: Refine Patterns

Based on testing: Add missing keywords Refine intent patterns to reduce false positives Adjust file path patterns Test content patterns against actual files

05
Step 5: Follow Anthropic Best Practices

✅ Keep SKILL.md under 500 lines ✅ Use progressive disclosure with reference files ✅ Add table of contents to reference files > 100 lines ✅ Write detailed description with trigger keywords ✅ Test with 3+ real scenarios before documenting

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.