progressive-disclosure

Restructure large documentation into slim indexes with on-demand detail directories.

15|12|Updated Jan 10, 2025
One-click install
npx skills add https://github.com/gptme/gptme-contrib --skill progressive-disclosure-gptme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progressive-disclosure
Source: https://github.com/gptme/gptme-contrib/tree/main/skills/progressive-disclosure
Command: npx skills add https://github.com/gptme/gptme-contrib --skill progressive-disclosure-gptme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large documentation files are frequently loaded in full, causing context bloat and slow response times. This skill provides a pattern to split monolithic docs into a slim index plus on-demand detail directories to improve accessibility and efficiency.

Core Features & Use Cases

  • Slim index (README) always included for quick navigation.
  • Detail directories loaded on-demand when deeper information is required.
  • Applies to product guides, API references, and knowledge bases to reduce token usage and speed up responses.

Quick Start

Use the slim index as the default entry and load topic-specific detail directories only when requested.

Frequently Asked Questions about progressive-disclosure

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

FAQPage Schema
How do I reduce context size when loading large documentation files?

Reduce context size by restructuring large documentation into a slim index with on-demand detail directories. This pattern splits monolithic docs so only the root entry is loaded initially, preventing context bloat and improving response times.

What is progressive disclosure for knowledge base navigation?

Progressive disclosure is a documentation structure pattern that provides a slim root index for quick navigation and loads topic-specific detail directories on-demand. It enables token-efficient access to product guides and references by separating the index from deeper information.

How do I structure product docs for on-demand loading?

Structure product docs by creating a root SKILL.md entry with YAML frontmatter defining name and description. Use this slim index as the default navigation point, placing deeper information into topic-specific directories that are loaded only when requested.

Does this documentation restructuring approach require external dependencies?

No external dependencies are required to implement this on-demand documentation structure. The pattern relies solely on a root entry file with YAML frontmatter and optional support for scripts, references, and assets to power deterministic tasks when invoked.

When should I split monolithic docs into a slim index?

Split monolithic docs into a slim index when sections are rarely needed together, causing context bloat and slow response times. This approach is applicable to knowledge bases, API references, and product guides where users navigate specific topics independently.

What is the best way to improve token efficiency for large guides?

The best way to improve token efficiency is to restructure large guides into a slim index plus on-demand detail directories. By loading topic folders only when deeper information is required, you reduce token usage and speed up responses.