skill-builder

Automate creation and optimization of Claude Code skills with progressive disclosure.

2|2|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/resolve-io/.prism --skill skill-builder-resolve-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-builder
Source: https://github.com/resolve-io/.prism/tree/main/skills/skill-builder
Command: npx skills add https://github.com/resolve-io/.prism --skill skill-builder-resolve-io

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Building efficient, scalable Claude Code skills can be complex, leading to token waste, slow performance, and difficult maintenance. This skill provides a structured approach to overcome these challenges, guiding you through best practices for token optimization and progressive disclosure.

Core Features & Use Cases

  • Progressive Disclosure: Learn to structure skills in layers (metadata, body, bundled) for optimal token usage and reduced cognitive load.
  • Token Optimization: Master techniques to keep metadata concise (~100 tokens) and skill bodies focused (<2k tokens), deferring details to bundled files.
  • Templates & Checklists: Access ready-to-use SKILL.md templates, process guides, and validation checklists for planning, structuring, and deploying your skills.
  • Use Case: When you need to create a new Claude Code skill, use this skill to guide you through the entire process, from initial planning to deployment, ensuring it's token-efficient and follows best practices.

Quick Start

Help me create a new Claude Code skill for incident triage. What are best practices for skill token optimization? Show me a SKILL.md template.

Frequently Asked Questions about skill-builder

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

FAQPage Schema
How do I structure a Claude skill to minimize token usage?

Structure skills in three progressive levels: metadata (~100 tokens in SKILL.md), body under 5k tokens with core logic, and bundled reference files deferred to Level 3. This three-level loading pattern reduces cognitive load and token waste by disclosing only essential information upfront.

What's the best practice for organizing Claude skill templates and deployment?

Use ready-to-use SKILL.md templates, process guides, and validation checklists to plan, structure, and deploy skills consistently. Templates ensure metadata stays concise, skill bodies remain focused under 2k tokens, and supporting details live in /reference files for deferred loading.

How do I create a new Claude skill from scratch?

Follow the three-level loading pattern: write Level 1 metadata in SKILL.md (~100 tokens), develop Level 2 body with core functionality (under 5k tokens), and organize Level 3 bundled reference files. Use provided templates and checklists to guide planning, structuring, and deployment.

Can I apply token optimization to existing Claude skills?

Yes. Refine existing skills by redistributing content across the three-level pattern: condense metadata to ~100 tokens, trim body to under 2k focused tokens, and move detailed references to bundled /reference files. This improves performance and reduces token overhead.

What are the token limits for each layer of a Claude skill?

Level 1 metadata targets ~100 tokens in SKILL.md, Level 2 body should stay under 5k tokens with core logic concentrated under 2k, and Level 3 bundled reference files hold supporting details. These limits enforce progressive disclosure and prevent token bloat.