Skill Builder

Create Claude Skills with YAML frontmatter and a standardized directory layout.

7|1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/pacphi/emailibrium --skill skill-builder-pacphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Builder
Source: https://github.com/pacphi/emailibrium/tree/main/.claude/skills/skill-builder
Command: npx skills add https://github.com/pacphi/emailibrium --skill skill-builder-pacphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating Claude Skills is error-prone without a consistent, scalable template. Skill Builder standardizes the process by providing a ready-to-use skeleton with strict YAML frontmatter and a progressive disclosure structure to ensure consistency across skills.

Core Features & Use Cases

  • Provides a minimal yet complete SKILL.md frontmatter with required fields (name and description) and safe defaults.
  • Enforces a 3-level progressive disclosure layout (Level 1: metadata, Level 2: body with Quick Start, Level 3+: references) to support scalable skill catalogs.
  • Supports optional resources in scripts/, references/, and assets/ to augment functionality when needed.
  • Useful for teams or individuals who want production-ready skill templates that are easy to customize and audit.

Quick Start

Create a new top-level skill directory and start with a SKILL.md that follows the YAML frontmatter format and the progressive disclosure structure.

Frequently Asked Questions about Skill Builder

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

FAQPage Schema
How do I create a Claude Skill with YAML frontmatter and a standardized directory layout?

To create a Claude Skill, you use a standardized template that enforces strict YAML frontmatter with required name and description fields, alongside a progressive disclosure directory layout for production-ready consistency.

What is the progressive disclosure structure for a SKILL.md file?

Progressive disclosure structures SKILL.md into three levels: Level 1 provides metadata, Level 2 contains the Quick Start body, and Level 3+ directs tools to optional references and assets for comprehensive guidance.

Do I need to include optional scripts and references directories when building a skill template?

No, scripts, references, and assets directories are optional resources used to augment functionality. They are only added to the skill directory when you need to support advanced capabilities beyond the core SKILL.md.

What's the best way to standardize multiple Claude Skills for team production use?

Standardizing multiple Claude Skills requires applying a consistent template with strict YAML frontmatter validation and a 3-level progressive disclosure layout, ensuring every skill is easy to customize and audit.

Why does my SKILL.md structure fail validation when creating a new skill?

SKILL.md validation fails if the required YAML frontmatter fields, specifically name and description, are missing, or if the file does not adhere to the expected progressive disclosure structure enforced by the template.