skill-developer

To create a Claude Code skill, define a SKILL.md file under .claude/skills/{name}/ with proper YAML frontmatter, then register it in .claude/skills/skill-rules.json following Anthropic best practices for naming conventions and documentation structure.

Claude Code skill triggers support keywords, intent patterns, file paths, and content patterns. You can also define skip conditions in the skill-rules.json configuration to control activation behavior and prevent unnecessary enforcement during unrelated sessions.

Claude Code skills use a two-hook architecture combining UserPromptSubmit and PreToolUse hooks to manage session tracking and progressive disclosure, ensuring governance rules are enforced at the right execution stage without overwhelming the context window.

Skill activation issues often stem from misconfigured trigger patterns in skill-rules.json or exceeding the 500-line limit in SKILL.md. Debug by verifying frontmatter syntax, checking enforcement levels, and running manual trigger tests to isolate the configuration failure.

Skill-rules.json supports configurable enforcement levels and skip conditions that dictate how strictly trigger patterns apply. These settings govern whether a skill actively modifies tool calls or passively provides context based on matching intent patterns and file paths.

The 500-line rule is a best practice guideline for Claude Code skills to maintain optimal context processing. Keeping your SKILL.md under 500 lines ensures efficient progressive disclosure and prevents trigger activation delays caused by oversized content.