skill-builder

Interview users to scaffold Claude Code skills with SKILL.md artifacts.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill skill-builder-testdouble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-builder
Source: https://github.com/testdouble/han/tree/main/han-plugin-builder/skills/skill-builder
Command: npx skills add https://github.com/testdouble/han --skill skill-builder-testdouble

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and building Claude Code skills requires a structured, evidence-driven process that translates ideas into production-ready SKILL.md artifacts, aligned with plugin-building guidance.

Core Features & Use Cases

  • Interview-driven design guides the user through an evidence-based interview to determine scope, naming, and workflow.
  • Guided authoring produces SKILL.md frontmatter and body that conform to governance and progressive-disclosure standards.
  • Artifact readiness generates a ready-to-review skill with references, scripts, and assets when needed.

Quick Start

Initiate the skill-building interview to draft and scaffold a new Claude Code skill.

Frequently Asked Questions about skill-builder

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

FAQPage Schema
How do I design and scaffold a new Claude Code skill?

To design a Claude Code skill, an interview-driven process guides naming, scope, and workflow decisions, mapping them to frontmatter fields and producing a ready-to-review SKILL.md artifact.

What is the best way to structure a SKILL.md file for plugin development?

The best way to structure a SKILL.md file is through guided authoring that conforms to governance and progressive-disclosure standards, ensuring frontmatter and body content align with plugin-building guidance.

Does building a Claude Code skill require an evidence-driven interview?

Yes, building a skill requires an evidence-driven interview to determine scope, naming, and workflow, ensuring the resulting skill design maps accurately to reference assets and governance guidance.

Can I generate testable outcomes when creating a new skill within a plugin ecosystem?

Yes, the skill-building workflow produces testable outcomes and a ready-to-review SKILL.md, generating necessary references, scripts, and assets for new skills within a plugin ecosystem.

What is progressive disclosure in the context of authoring SKILL.md files?

Progressive disclosure in authoring SKILL.md files is a governance standard that structures frontmatter and body content, ensuring the skill design reveals complexity progressively and conforms to plugin-building guidance.

Why are mapping decisions important for frontmatter fields in skill building?

Mapping decisions to frontmatter fields is important because it translates evidence-driven interview insights into production-ready SKILL.md artifacts, ensuring proper naming, scope, and workflow alignment.