Progressive Disclosure

Community

Neeeophytee

progressive-disclosure

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

Overview

Publisher	Neeeophytee
Repository	`finding-unknowns-skills`
Skill name	`progressive-disclosure`
Stars	353
Forks	28
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Neeeophytee on GitHub. Read the source before you install it.

Installation

Install the Progressive Disclosure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/progressive-disclosure
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/progressive-disclosure

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git /tmp/finding-unknowns-skills
mkdir -p .claude/skills
cp -r /tmp/finding-unknowns-skills/skills/progressive-disclosure .claude/skills/progressive-disclosure

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Progressive Disclosure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Progressive Disclosure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Progressive Disclosure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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.
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.
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.
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.
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.
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.

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.

Frequently asked questions

What does the Progressive Disclosure AI skill do?

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

Why use Progressive Disclosure on TypingMind?

Because you install it once and use it with any model. Progressive Disclosure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Progressive Disclosure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/progressive-disclosure. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Progressive Disclosure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Progressive Disclosure?

As many as you like. As long as a model supports skills, you can use Progressive Disclosure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Progressive Disclosure AI skill free?

Yes. It is published on GitHub by Neeeophytee under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brainstorming

obra

CommunityPopular

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Progressive disclosure

Steps

Guardrails

Frequently asked questions

Related AI Skills

Set up your own AI workspace now