skill-developer

Create and maintain Claude Code skills with YAML frontmatter and hook mechanics.

Updated Dec 13, 2024
One-click install
npx skills add https://github.com/neo-picasso-2112/dotfiles --skill skill-developer-neo-picasso-2112
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/neo-picasso-2112/dotfiles/tree/main/.claude/backup/.claude/skills/skill-developer
Command: npx skills add https://github.com/neo-picasso-2112/dotfiles --skill skill-developer-neo-picasso-2112

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a comprehensive framework for creating and managing Claude Code skills, aligning with Anthropic best practices, progressive disclosure, and the 500-line rule to ensure maintainable, safe skill ecosystems.

Core Features & Use Cases

  • Two-hook architecture overview and practical patterns for UserPromptSubmit and PreToolUse hooks to enable proactive skill activation and gentle reminders.
  • Clear skill construction: YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels, and skip conditions to prevent repetitive prompts.
  • Reference-material driven development: guidance on testing, debugging, and expanding skill rules, with reusable reference documents to keep SKILL.md under 500 lines.

Quick Start

Create a new skill in .claude/skills/{skill-name}/SKILL.md following the frontmatter template, then add it to .claude/skills/skill-rules.json and test triggers.

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 follows Anthropic best practices?

To create a Claude Code skill, define a SKILL.md file with YAML frontmatter, specify trigger patterns, and register it in skill-rules.json to ensure progressive disclosure and maintainable skill ecosystems.

What are UserPromptSubmit and PreToolUse hooks in skill development?

UserPromptSubmit and PreToolUse hooks are mechanisms enabling proactive skill activation and gentle reminders, allowing Claude Code skills to trigger automatically based on user intent and tool usage context.

How does the 500-line rule affect skill maintenance?

The 500-line rule enforces safe development by keeping SKILL.md files concise, using reusable reference documents to maintain readability and prevent overly complex skill definitions.

What trigger patterns can I use to activate a Claude Code skill?

Trigger patterns include keywords, intent patterns, file paths, and content patterns, allowing skills to activate contextually while enforcing skip conditions to prevent repetitive prompts.

How do I test and debug Claude Code skill triggers?

Test skill triggers by adding the skill to skill-rules.json and validating activation patterns through reference-material driven development, which provides concrete testing guidance and structured debugging workflows.

Can I use progressive disclosure to manage complex skill rules?

Progressive disclosure allows complex skill rules to be managed through reusable reference documents, keeping the main SKILL.md under 500 lines while preserving detailed implementation guidance.