skill-creator

Generate modular Claude Skills with progressive disclosure and YAML frontmatter.

146|31|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm --skill skill-creator-bobmatnyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/bobmatnyc/claude-mpm/tree/main/src/claude_mpm/skills/bundled/main/skill-creator
Command: npx skills add https://github.com/bobmatnyc/claude-mpm --skill skill-creator-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires quick_validate, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Provide a structured approach for creating or updating Claude Skills, with progressive-disclosure patterns to keep entry points lean while documenting deeper knowledge in references.

Core Features & Use Cases

  • Progressive-disclosure skill structure (metadata, entry point, references)
  • Reusable components: scripts, references, assets
  • Guidance for packaging, testing, and iteration
  • Example-driven workflow for skill creation

Quick Start

  1. Understand the skill with concrete examples
  2. Plan reusable components (scripts/references/assets)
  3. Initialize with scripts/init_skill.py
  4. Edit SKILL.md and resources
  5. Package and validate
  6. Iterate

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a Claude Skill with proper structure and packaging?

Create Claude Skills by planning reusable components, scaffolding directories with scripts/init_skill.py, writing YAML frontmatter in SKILL.md, following kebab-case naming, and organizing entry points (140–160 lines) with references (150–500 lines each). This structured approach ensures technical compliance and distribution readiness.

What is progressive disclosure in Skill design?

Progressive disclosure keeps Skill entry points lean and focused while documenting deeper knowledge in separate reference documents. This pattern helps users understand core functionality immediately without overwhelming them with advanced details, improving usability across complex domains.

Can I reuse components across multiple Claude Skills?

Yes. Design reusable scripts, references, and assets as modular components during planning, then package them for distribution. This approach reduces duplication, accelerates skill creation and updates, and maintains consistency across your Skill ecosystem.

What are the technical requirements for Claude Skill packaging?

Claude Skills require YAML frontmatter in SKILL.md, kebab-case directory naming, entry point sizing of 140–160 lines, and references organized at 150–500 lines each. The quick_validate tool and Python support packaging validation and initialization workflows.

How do I iterate and test a new Skill before distribution?

Initialize your Skill with scripts/init_skill.py, edit SKILL.md and resources, package and validate using quick_validate, then iterate based on results. This workflow ensures your Skill meets technical requirements before release.

What's the best way to plan components for a complex Skill?

Start by understanding the skill domain with concrete examples, then identify reusable scripts, references, and assets that serve multiple use cases. Map dependencies and entry point logic before scaffolding, reducing rework during implementation.