Skill Builder

Create Claude Skills with YAML frontmatter and a structured SKILL.md body.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/nickm538/wifi-sensing-advanced --skill skill-builder-nickm538
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Skill Builder
Source: https://github.com/nickm538/wifi-sensing-advanced/tree/main/.claude/skills/skill-builder
Command: npx skills add https://github.com/nickm538/wifi-sensing-advanced --skill skill-builder-nickm538

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating Claude Skills often requires consistent frontmatter, structure, and documentation scaffolding; this guide helps teams produce production-ready Skill definitions with minimal friction.

Core Features & Use Cases

  • Enforces YAML frontmatter with required fields and a standard SKILL.md layout.
  • Provides a progressive-disclosure structure (metadata, SKILL.md body, and references) to scale beyond 100+ skills.
  • Includes templates and guidelines to standardize skill creation across projects and teams.

Quick Start

Create a top-level skill directory named after the skill and place a properly formatted SKILL.md with YAML frontmatter and a clean, 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 proper YAML frontmatter?▼

A Claude Skill requires a SKILL.md file with required YAML frontmatter fields and a structured body. This enforces consistent skill definitions and ensures discoverability across Claude surfaces.

What is progressive disclosure in Claude Skill documentation?▼

Progressive disclosure in skill documentation layers metadata, the SKILL.md body, and references. This structure scales efficiently beyond 100+ skills while maintaining readability and safety.

How do I standardize skill creation across multiple projects and teams?▼

Standardize skill creation across projects by applying a reusable template that enforces a 4-level SKILL.md structure. This provides consistent documentation scaffolding with minimal friction for teams.

Do I need any dependencies to generate a production-ready Skill definition?▼

No dependencies are required to generate a production-ready Skill definition. The builder operates independently to provide templates, validation guidance, and structured formatting for safe skill creation.

What's the best way to structure a SKILL.md file for Claude surfaces?▼

Structure a SKILL.md file using a 4-level layout: YAML frontmatter, the SKILL.md body, optional scripts or resources, and validation guidance. This ensures discoverability and safety across surfaces.

When should I use a skill template instead of writing documentation from scratch?▼

Use a skill template when you need consistent frontmatter and documentation scaffolding across multiple skills. It eliminates manual formatting errors and accelerates production-ready skill creation for teams.