Agent skill

Progressive Disclosure

by Neeeophytee in Neeeophytee/finding-unknowns-skills

Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.

MITAuto-check passedAgent Workflows

Install Progressive Disclosure

skills CLI
$ npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Neeeophytee/finding-unknowns-skills progressive-disclosure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/progressive-disclosure .claude/skills/progressive-disclosure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
progressive-disclosure
GitHub stars
343
Token cost
~660 tokens
SKILL.md length
422 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.

  • Works in 6 steps: Read the whole artifact and identify its… → Sort every section into two piles:… → Keep the universal core in the entry… → …
  • Tasks that involve Agent instruction files
  • SKILL.md covers Steps and Guardrails
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Progressive Disclosure is an agent skill from Neeeophytee/finding-unknowns-skills. Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent instruction files. The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.

When your agent uses it

  • Tasks that involve Agent instruction files

Example prompts

  • “/progressive-disclosure”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read the whole artifact and identify its branches — the genuinely different ways a run can go through it. A verification section reached…
  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…
  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…
  4. Move each branch into a sibling file named for what it holds, not for where it came from — verification.md, glossary.md — so the name…
  5. Write the pointer with care, because the pointer's wording is what decides whether the material is ever reached. Name the condition and…
  6. Walk each branch end to end and confirm it still has everything it needs. Then report what moved, what stayed, and the new size of the…

What it can do on your machine

Read from SKILL.md and the folder at commit ca5696a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Progressive Disclosure loads about 660 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 422 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~660

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 422 words, ~660 tokens.

Download SKILL.mdSave it as .claude/skills/progressive-disclosure/SKILL.md (or your agent's skills folder).
name
progressive-disclosure
description
Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
disable-model-invocation
true

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 — so the name alone tells the reader when to open it.
  5. Write the pointer with care, because the pointer's wording is what decides whether the material is ever reached. Name the condition and the file together: "when the change touches migrations, read migrations.md before planning." A bare link at the bottom of a file is not a pointer.
  6. Walk each branch end to end and confirm it still has everything it needs. Then report what moved, what stayed, and the new size of the entry file.
Show full SKILL.md (123 more words)Show less

Guardrails

  • Splitting is not deleting. If a section is genuinely dead, say so and remove it outright rather than hiding it in a file nobody opens.
  • Never split material that every branch needs. Two files that are always read together are one file with extra steps.
  • A pointer that never fires has made the material invisible, which is worse than leaving it inline. When the triggering condition can't be stated crisply, that section stays put.
  • Verify that the target harness actually ships sibling files alongside SKILL.md before relying on them; installers differ, and a pointer to a file that didn't travel is a broken skill.
  • Stop when the entry file is legible. Splitting past that point trades one kind of unreadability for another.

© Neeeophytee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/progressive-disclosure of Neeeophytee/finding-unknowns-skills.

Open the folder on GitHubat commit ca5696a

Compare with similar skills

Progressive Disclosure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Progressive Disclosure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Progressive Disclosure this skillNeeeophytee/finding-unknowns-skills343—~660Automated safety check: PassMIT
Using Agent Skillsaddyosmani/agent-skills103k4 repos~2.4kAutomated safety check: PassMIT
Claude ReflectBayramAnnakov/claude-reflect1.7k2 repos~627Automated safety check: PassMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Writing For Agentsbestofjs/bestofjs3.1k18 repos~2.7kAutomated safety check: PassMIT
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Using Agent Skills

    addyosmani/agent-skills

    Meta-skill for choosing which workflow skill fits the task at hand, plus always-on habits: surface assumptions, stop on confusion, push back, keep it simple and stay in scope.

    103k GitHub starsUsed in 4 repos~2.4k tokens
    Agent WorkflowsAuto-check passed
  • Claude Reflect

    BayramAnnakov/claude-reflect

    Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md.

    1.7k GitHub starsUsed in 2 repos~627 tokens
    Agent WorkflowsAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • Writing For Agents

    bestofjs/bestofjs

    Writing documents for agents. An agent skill from bestofjs/bestofjs.

    3.1k GitHub starsUsed in 18 repos~2.7k tokens
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed
  • SkillOpt Sleep Cycle

    microsoft/SkillOpt

    Official

    Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.

    18k GitHub stars~2.3k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

More from Neeeophytee/finding-unknowns-skills

All 14 skills in this repo
  • Agent Interface Design

    Neeeophytee/finding-unknowns-skills

    Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.

    343 GitHub stars~650 tokensUpdated 11 days ago
    Auto-check passed
  • Assumption Test

    Neeeophytee/finding-unknowns-skills

    Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.

    343 GitHub stars~631 tokensUpdated 11 days ago
    Auto-check passed
  • Blindspot Pass

    Neeeophytee/finding-unknowns-skills

    Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.

    343 GitHub stars~482 tokensUpdated 11 days ago
    Auto-check passed
  • Brainstorm Prototypes

    Neeeophytee/finding-unknowns-skills

    Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.

    343 GitHub stars~492 tokensUpdated 11 days ago
    Auto-check passed
  • Change Quiz

    Neeeophytee/finding-unknowns-skills

    After a working session, produce a report on what changed plus a quiz the user must pass before merging.

    343 GitHub stars~532 tokensUpdated 11 days ago
    Auto-check passed
  • Context Audit

    Neeeophytee/finding-unknowns-skills

    Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.

    343 GitHub stars~779 tokensUpdated 11 days ago
    Auto-check passed

Categories

Questions about Progressive Disclosure

What does Progressive Disclosure do?

Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed. Progressive Disclosure is an agent skill from Neeeophytee/finding-unknowns-skills.md, or spec into an entry file plus files that load only when they're needed.

When should I use Progressive Disclosure?

Progressive Disclosure fits situations like: tasks that involve Agent instruction files.

How do I install Progressive Disclosure in Claude Code?

Run `npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure -a claude-code`. Or copy the skill folder (skills/progressive-disclosure in Neeeophytee/finding-unknowns-skills) into .claude/skills/progressive-disclosure in your project. Claude Code loads it when a task matches its description.

How do I install Progressive Disclosure in Codex?

Run `npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure -a codex`. Or copy the skill folder (skills/progressive-disclosure in Neeeophytee/finding-unknowns-skills) into .agents/skills/progressive-disclosure in your project. Codex loads it when a task matches its description.

Can I use Progressive Disclosure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Neeeophytee/finding-unknowns-skills --skill progressive-disclosure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/progressive-disclosure, .gemini/skills/progressive-disclosure, .github/skills/progressive-disclosure and .opencode/skills/progressive-disclosure in your project.

What does Progressive Disclosure need to run?

SKILL.md names no scripts, command-line tools or credentials: Progressive Disclosure is instructions for the agent only.

Does Progressive Disclosure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Progressive Disclosure safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Progressive Disclosure use?

Progressive Disclosure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Progressive Disclosure use?

About 660 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Progressive Disclosure?

Skills that share tags, products or a category with Progressive Disclosure: Using Agent Skills (addyosmani/agent-skills, 103k stars), Claude Reflect (BayramAnnakov/claude-reflect, 1.7k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Writing For Agents (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Progressive Disclosure?

Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.

Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.