Skill Development

Guides creation of Claude Code plugin skills with progressive disclosure structure.

1|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/voxxov222/Claude-code- --skill skill-development-voxxov222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Development
Source: https://github.com/voxxov222/Claude-code-/tree/main/temp-repo/plugins/plugin-dev/skills/skill-development
Command: npx skills add https://github.com/voxxov222/Claude-code- --skill skill-development-voxxov222

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating effective skills for Claude Code plugins requires understanding SKILL.md frontmatter conventions, trigger phrase design, and progressive disclosure principles, which are easy to get wrong without structured guidance. ## Core Features & Use Cases - Skill Creation Workflow: Follows a six-step process from understanding use cases through planning resources, structuring directories, editing SKILL.md, validating, and iterating. - Progressive Disclosure Guidance: Explains what content belongs in SKILL.md versus references/, examples/, and scripts/ to keep context usage lean. - Writing Style Enforcement: Defines imperative/infinitive form requirements and third-person description conventions with concrete good and bad examples. - Use Case: When adding a new skill to a Claude Code plugin, use this Skill to generate a properly structured skill directory with a lean SKILL.md, specific trigger phrases, and correctly organized bundled resources. ## Quick Start Ask the AI to create a new skill for your plugin following the skill development best practices and structure guidelines.

Frequently Asked Questions about Skill Development

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

FAQPage Schema
How do I create a skill for a Claude Code plugin?

Create a directory under the plugin's skills/ folder containing a SKILL.md file with YAML frontmatter defining name and description. Follow the six-step process: understand use cases, plan reusable resources, create the structure, edit SKILL.md, validate, and iterate.

What should go in a SKILL.md description field?

The description should use third person with specific trigger phrases users would say, such as "create a hook" or "configure settings". Avoid vague descriptions or second-person phrasing, as the description determines when the skill activates.

When should content go in references instead of SKILL.md?

Move detailed patterns, API documentation, migration guides, and edge cases to references/ files when SKILL.md exceeds roughly 2,000 words. Keep only core concepts, essential workflows, and pointers to resources in SKILL.md itself.

How does progressive disclosure work in Claude Code skills?

Progressive disclosure uses three loading levels: metadata stays always in context, the SKILL.md body loads when the skill triggers, and bundled resources load only as needed. This keeps context usage efficient while supporting detailed documentation.

Why is second-person writing discouraged in skill files?

Skills are written for another Claude instance to consume, so imperative verb-first instructions maintain consistency and clarity. Phrases like "you should configure" are replaced with direct commands like "configure the server".