skill-development

Design and write reusable Claude Code plugin skills with metadata and progressive disclosure.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Wizarck/eligia-skills --skill skill-development-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-development
Source: https://github.com/Wizarck/eligia-skills/tree/main/claude-plugins-official/plugins/plugin-dev/skills/skill-development
Command: npx skills add https://github.com/Wizarck/eligia-skills --skill skill-development-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps create and refine reusable Claude Code plugin skills with clear triggers, strong structure, and progressive disclosure, so new skills are easier to discover, easier to use, and easier to maintain.

Core Features & Use Cases

  • Skill design guidance: Shape a new skill from concrete user scenarios into a focused, reusable workflow.
  • Metadata and trigger tuning: Write frontmatter that uses specific trigger phrases and supports reliable discovery.
  • Content organization: Decide what belongs in SKILL.md versus supporting references, scripts, and assets.
  • Progressive disclosure: Keep the main skill lean while moving detailed patterns, examples, and utilities into bundled resources.
  • Validation and iteration: Check structure, writing style, references, and packaging readiness before shipping a skill.
  • Use case: Create a plugin skill for hook development, then split validation logic into scripts, patterns into references, and templates into assets.

Quick Start

Draft a new skill-development skill by defining its trigger phrases, outlining the required workflow, and linking any supporting references or utilities.

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 Claude Code plugin skill with proper frontmatter and triggers?

To create a Claude Code plugin skill, you define frontmatter with a specific name and description, then write an imperative instructional body. This structures your skill for reliable discovery and clear execution triggers.

What is progressive disclosure when organizing a Claude plugin skill?

Progressive disclosure keeps the main SKILL.md lean by moving detailed patterns, examples, and utilities into bundled references, scripts, and assets. This makes new skills easier to maintain and use.

How do I validate and refactor an existing Claude Code skill?

You validate a Claude Code skill by checking its structure, writing style, references, and packaging readiness. Refactoring involves tuning trigger phrases and reorganizing content using progressive disclosure.

What should go into SKILL.md versus supporting references and scripts?

SKILL.md should contain the lean, imperative workflow instructions, while supporting references hold detailed patterns. Scripts handle validation logic, and assets store templates, ensuring clear content organization.

Can I use this approach to design a skill for any type of plugin development workflow?

Yes, you can shape a new skill from concrete user scenarios into a focused, reusable workflow. This applies to various plugin development tasks, including hook development and validation logic splitting.

Why does my Claude Code skill fail to trigger reliably during searches?

Unreliable skill triggers usually stem from poorly written frontmatter. Tuning your metadata to use specific trigger phrases and applying progressive disclosure supports reliable discovery and packaging readiness.