skill-creator

Design Claude Skills using a three-level progressive-disclosure workflow.

35|2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/spences10/claude-code-toolkit --skill skill-creator-spences10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/spences10/claude-code-toolkit/tree/main/plugins/toolkit-skills/skills/skill-creator
Command: npx skills add https://github.com/spences10/claude-code-toolkit --skill skill-creator-spences10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams to design Claude Skills using a disciplined, scalable approach so that skills are easy to maintain and extend.

Core Features & Use Cases

  • Progressive disclosure model: Level 1 metadata, Level 2 instructions, Level 3 resources keep content lean and context-efficient.
  • Structured templates: recommended directories (references, scripts, assets) with clear roles.
  • Guided workflow: from planning to deployment with references and tooling patterns.

Quick Start

Create a new skill by writing a lean SKILL.md with frontmatter, then add optional references and scripts as needed.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
What is progressive disclosure in skill architecture and when do I need it?

Progressive disclosure is a skill architecture design pattern that organizes content into a 3-level loading system: Level 1 metadata, Level 2 instructions, and Level 3 resources. You need it when designing Claude Skills to keep context lean, scalable, and easy to maintain across projects.

How do I design a Claude Skill using a structured workflow?

To design a Claude Skill, start by writing a lean SKILL.md with frontmatter to define Level 1 metadata. Then, add Level 2 instructions and optional Level 3 resources like references, scripts, and assets in recommended directories to structure the skill architecture.

Does this skill design approach work for organizing complex skill content across multiple projects?

Yes, this skill design approach uses a progressive-disclosure workflow with structured templates and clear roles for directories. It applies when planning new skills, organizing skill architecture, or writing skill content across projects, ensuring skills remain scalable and easy to extend.

What's the best way to structure Claude Skill directories and resources?

The best way to structure Claude Skill directories is using recommended folders like references, scripts, and assets with clear roles. This structured template approach keeps content lean and context-efficient by separating Level 2 instructions from Level 3 resources.

Why does my Claude Skill architecture become hard to maintain and extend?

Your Claude Skill architecture becomes hard to maintain when it lacks a disciplined progressive-disclosure model. Without a 3-level loading system separating metadata, instructions, and resources, content grows unmanageable and consumes excessive context.

Do I need to write a SKILL.md file to create a new skill?

Yes, you need to write a SKILL.md file to create a new skill. Start with a lean SKILL.md containing frontmatter for Level 1 metadata, then add optional references and scripts as needed to complete the skill architecture.