skill-developer

Author Claude Code skills with SKILL.md frontmatter and trigger rules.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill skill-developer-joshka0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/joshka0/foxctl/tree/main/docs/knowledge/skill-developer
Command: npx skills add https://github.com/joshka0/foxctl --skill skill-developer-joshka0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the confusion and trial-and-error involved in creating Claude Code skills that correctly trigger, follow Anthropic best practices, and behave safely and predictably via hook-driven activation.

Core Features & Use Cases

  • Skill authoring best practices: guidance on SKILL.md structure, YAML frontmatter requirements, naming conventions, and keeping content within the 500-line rule.
  • Trigger design & debugging: detailed coverage of keyword, intent-pattern (regex), file-path (glob), and content-pattern (regex) triggers, including tuning to reduce false positives/negatives.
  • Hook and enforcement mechanics: explains UserPromptSubmit and PreToolUse hook flows, exit-code behavior (including BLOCK via stderr), session tracking, and skip conditions for controlled enforcement.
  • Progressive disclosure workflows: recommends linking to reference documents and organizing deep details away from the main skill entry point.
  • Use when you are implementing a new skill, modifying skill-rules.json, or diagnosing why activation suggestions or guardrail blocks aren’t occurring as expected.

Quick Start

Use the skill-developer guide to create a new entry at .claude/skills/{your-skill}/SKILL.md and then validate that your triggers fire by testing the UserPromptSubmit hook with your prompt.

Frequently Asked Questions about skill-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code skill that triggers correctly based on user prompts?

To create a Claude Code skill, author a SKILL.md file with mandatory YAML frontmatter (name and description), then tune skill-rules.json triggers using keywords, intent regex, file globs, and content regex to match user prompts and repository evidence.

What are the hook enforcement mechanics for Claude Code skills?

Claude Code skills use UserPromptSubmit and PreToolUse hook flows to enforce guardrails. Hooks use exit codes to block via stderr, track sessions, and apply skip conditions to control activation behavior safely and predictably.

Why is my Claude Code skill not triggering or activating when expected?

Skill activation fails when trigger patterns in skill-rules.json are mistuned. Debug by testing the UserPromptSubmit hook with your prompt, verifying keyword, intent regex, file glob, and content regex patterns to reduce false positives and negatives.

What is progressive disclosure in Claude Code skill development?

Progressive disclosure in skill development means keeping the main SKILL.md entry point concise—within the 500-line rule—and linking to reference documents for deep details, organizing content so users get essential information first without overload.

How do I configure skill-rules.json trigger patterns to reduce false positives?

Tune skill-rules.json triggers by refining keywords, intent regex patterns, file-path globs, and content regex patterns. Test the UserPromptSubmit hook with representative prompts to verify activation suggestions fire correctly and reduce false matches.

What YAML frontmatter is required for a Claude Code SKILL.md file?

A Claude Code SKILL.md file requires mandatory YAML frontmatter containing the name and description fields. These fields ensure the skill is discovered and activated correctly based on user prompts and repository evidence.