progressive-disclosure
Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Progressive disclosure A long instruction file is paid for on every single turn, including the turns that need none of it. The fix is not deletion — the material is real — but placement: keep what every run needs in the entry file, and move what only some runs need behind a pointer that fires when it's relevant. This skill restructures one artifact. To find out which artifacts need it, audit first. ## Steps 1. Read the whole artifact and identify its **branches** — the genuinely different ways a run can go through it. A verification section reached only when the user asks to verify is a branch; a rule that applies every time is not. 2. Sort every section into two piles: needed on every branch, and needed on one. The split is the entire decision, and it is usually less even than it looks — most files are a short universal core wrapped in branch-specific detail. 3. Keep the universal core in the entry file, ordered so the file still reads coherently on its own. An entry file that no longer makes sense without its children has been cut in the wrong place. 4. Move each branch into a sibling file named for what it holds, not for where it came from — `verification.md`, `glossary.md` —
- Steps
- Guardrails
What does the progressive-disclosure skill do?
Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
How do I install it?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Neeeophytee/finding-unknowns-skills, a repository with 298 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.