Skill Development

Design Claude Code plugin skills with SKILL.md structure and progressive disclosure.

3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/HanHan666666/linglong-store-skill --skill skill-development-hanhan666666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Development
Source: https://github.com/HanHan666666/linglong-store-skill/tree/main/.agents/skills/skill-development
Command: npx skills add https://github.com/HanHan666666/linglong-store-skill --skill skill-development-hanhan666666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design and document Claude Code plugin skills with clear structure and best practices. It addresses the need for consistent skill templates, lean core documentation, and effective progressive disclosure to references and examples.

Core Features & Use Cases

  • Standardized skill templates with proper SKILL.md frontmatter and body
  • Progressive disclosure: move detailed content to references/ and examples/ and load them on demand
  • Guidance on writing style: imperative/infinitive form, third-person description, and frontmatter conventions
  • Templates and patterns for plugin skills to accelerate creation and iteration

Quick Start

Create a new skill directory following the standard layout:

  • SKILL.md with frontmatter including name and description
  • optional references/ for detailed patterns and API references
  • optional examples/ for working examples
  • optional scripts/ for utilities Demonstrate the skill usage by loading it in a plugin environment and validating progressive disclosure.

Frequently Asked Questions about Skill Development

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

FAQPage Schema
How do I structure a Claude Code plugin skill with proper frontmatter and progressive disclosure?

Organize your skill with frontmatter in SKILL.md containing name and description, then move detailed content to optional references/ and examples/ directories. Progressive disclosure loads content on demand, keeping the core documentation lean and discoverable while detailed patterns and working examples remain accessible separately.

What's the standard template layout for creating a new Claude Code plugin skill?

Create a skill directory with SKILL.md (frontmatter + body), optional references/ for API patterns and detailed guidance, optional examples/ for working demonstrations, and optional scripts/ for utilities. This standardized layout accelerates creation, ensures consistent discovery, and enables reliable reuse across plugin environments.

How do I write effective skill documentation following best practices for Claude Code?

Use imperative or infinitive form in descriptions, write in third person for frontmatter, enforce lean SKILL.md bodies, and apply progressive disclosure to load references and examples only when needed. These conventions ensure clarity, reduce cognitive load, and make skills reliably discoverable and usable by teams.

When should I use progressive disclosure to organize skill content into separate references and examples?

Apply progressive disclosure whenever detailed patterns, API references, or extended examples would bloat your core SKILL.md. Moving this content to references/ and examples/ directories keeps initial documentation focused, improves scannability, and lets users access depth only when they need it.

Can I reuse the standard skill resource layout across multiple plugin skills?

Yes. The standardized layout with frontmatter conventions, references/, examples/, and scripts/ directories is designed as a reusable pattern. This consistency accelerates skill creation, enables teams to iterate faster, and ensures reliable discovery and use across your plugin skill library.