skill-developer

To create a Claude Code skill, add a folder under .claude/skills with a SKILL.md file containing YAML frontmatter and a corresponding entry in skill-rules.json, then test the triggers using manual commands. This ensures proper skill activation and governance.

Claude Code skill activation supports keyword triggers, intent patterns, file paths, and content patterns. These trigger types are defined in the skill-rules.json file and governed by enforcement levels with hook mechanisms like UserPromptSubmit and PreToolUse.

Skill activation debugging requires checking frontmatter compliance, validating trigger rules in skill-rules.json, and verifying hook mechanisms like UserPromptSubmit and PreToolUse. Progressive disclosure workflows and session tracking references help troubleshoot activation flow issues.

Setting up a Claude Code skill requires a SKILL.md file with YAML frontmatter and a skill-rules.json entry. Reference materials and documentation scaffolding ensure compliance with structural requirements and the 500-line rule for skill content.

Yes, Claude Code skills support enforcement hooks including UserPromptSubmit and PreToolUse with session tracking. These mechanisms govern when skills activate and provide troubleshooting references for debugging activation flows across frontmatter and trigger rules.

The 500-line rule is a compliance constraint enforced during Claude Code skill creation, limiting skill file length. It applies to all skill content governed by the skill developer framework, ensuring skills maintain manageable progressive disclosure workflows.