Skill Development

Create and organize Claude Code skills with triggers, instructions, and resources.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ricable/mcai --skill skill-development-ricable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Development
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/skill-development
Command: npx skills add https://github.com/ricable/mcai --skill skill-development-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps design, organize, and refine Claude Code skills so they are easy to trigger, easy to maintain, and reliable to use. It reduces vague descriptions, bloated instructions, and missing resources by enforcing a clear skill structure and reusable content.

Core Features & Use Cases

  • Skill planning: Define concrete triggers, user scenarios, and the intended behavior of a new skill.
  • Skill structure: Separate core instructions from detailed references, scripts, and assets using progressive disclosure.
  • Metadata quality: Write strong frontmatter, including a specific name and trigger-rich description.
  • Validation workflow: Check directory layout, resource references, writing style, and completeness before publishing.
  • Use Case: A team wants to add a new internal skill for hook development, so this skill helps draft the instructions, organize examples and references, and verify the final package is ready for Claude Code.

Quick Start

Describe the skill you want to create or improve, then follow this guide to define its trigger phrases, structure its resources, and validate the final SKILL.md.

Frequently Asked Questions about Skill Development

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

FAQPage Schema
How do I structure Claude Code skills to avoid bloated instructions and missing resources?

To structure Claude Code skills effectively, separate core instructions from detailed references and scripts using progressive disclosure. This approach ensures skills remain easy to trigger, easy to maintain, and reliable by enforcing a clear directory layout and reusable content.

What is progressive disclosure in skill development and workflow design?

Progressive disclosure in skill development is a design pattern that separates lean, imperative core instructions from supporting references, scripts, and assets. It allows Claude Code to process triggers quickly without loading unnecessary details until they are explicitly needed.

How do I write YAML frontmatter and trigger-rich descriptions for a new skill?

Writing YAML frontmatter requires defining a specific name and a trigger-rich description that clearly outlines the intended behavior and user scenarios. You must use imperative body writing to ensure the skill is easy to trigger and its metadata remains valid.

Can I use Claude Code to validate skill metadata and directory structure before publishing?

Yes, you can validate skill metadata and directory structure before publishing by following a specific validation workflow. This process checks directory layout, resource references, writing style, and completeness to ensure the final package is ready for Claude Code.

What is the best way to plan and organize a new skill for hook development?

The best way to plan a new skill for hook development is to define concrete triggers, user scenarios, and intended behavior first. Then, organize examples and references structurally to separate core logic from detailed assets.

Why does my Claude Code skill fail to trigger or behave unreliably?

Claude Code skills fail to trigger or behave unreliably due to vague descriptions, bloated instructions, or missing resources. Validating skill metadata, ensuring strong YAML frontmatter, and applying progressive disclosure resolves these structural issues.