apply-progressive-disclosure

Fragment CLAUDE.md and SKILL.md files into lazy-loaded components to reduce startup token load.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/VitorAndTxr/omni-sw --skill apply-progressive-disclosure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-progressive-disclosure
Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/apply-progressive-disclosure
Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill apply-progressive-disclosure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progressive Disclosure optimizes Claude Code configurations by fragmenting large CLAUDE.md/SKILL.md content into lazy-loaded components to reduce startup token costs and improve load times.

Core Features & Use Cases

  • Fragment CLAUDE.md and SKILL.md into targeted references and scripts to minimize tokens loaded on startup.
  • Analyze, optimize, and report token budgets across project roots and skill directories.
  • Generate before/after context reports to guide manual migration and deduplication.

Quick Start

Analyze a repository or skill to generate a token-budget report and apply fragmentation to reduce startup load.

Frequently Asked Questions about apply-progressive-disclosure

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

FAQPage Schema
How do I reduce startup token costs in Claude Code configurations?

Reduce startup token costs by fragmenting large CLAUDE.md and SKILL.md files into lazy-loaded targeted references and scripts using progressive disclosure. This minimizes the tokens loaded on startup to optimize Claude Code configurations.

What is progressive disclosure for Claude Code skill management?

Progressive disclosure for Claude Code skill management is an optimization technique that fragments large configuration files into lazy-loaded components. It analyzes token budgets across project roots and skill directories to minimize startup load and deduplicate content.

How do I analyze and optimize token budgets across project directories?

Analyze and optimize token budgets by generating before/after context reports across project roots and skill directories. This workflow requires a CLI analysis tool and fragmentation-rules references to guide manual migration and deduplication of configuration artifacts.

Can I fragment SKILL.md files to minimize tokens loaded on startup?

Yes, you can fragment SKILL.md files to minimize tokens loaded on startup. The progressive disclosure process operates on skill directories containing SKILL.md, extracting code and applying fragmentation rules to create targeted references and scripts.

Do I need a CLI analysis tool to apply progressive disclosure to configurations?

Yes, applying progressive disclosure requires a CLI analysis tool to evaluate token budgets and generate before/after reports. Optional scripting is also utilized to fragment documents and extract code during the optimization workflow.

What are the limitations of fragmenting CLAUDE.md for token optimization?

A limitation of fragmenting CLAUDE.md is that it requires manual migration guided by generated before/after context reports. The fragmentation process relies on specific rules and optional scripting, meaning deduplication and optimization are not fully automated.