doc-organizer

Organize documentation into hierarchical Progressive Disclosure layers with README index files.

7|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/Tempuss/agent-hub --skill doc-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-organizer
Source: https://github.com/Tempuss/agent-hub/tree/main/skills/doc-organizer
Command: npx skills add https://github.com/Tempuss/agent-hub --skill doc-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill tackles overwhelming and disorganized documentation, restructuring it into a clear, hierarchical system based on Progressive Disclosure. It drastically reduces token usage and improves navigability, saving users time and cognitive load.

Core Features & Use Cases

  • Progressive Disclosure: Organizes information from high-level overviews to detailed specifics.
  • Token Optimization: Achieves 95%+ reduction in context window usage for AI interactions.
  • Use Case: Restructure a large, chaotic project documentation repository into an intuitive, easy-to-navigate knowledge base with auto-generated README files for each section.

Quick Start

Organize the existing project documentation for the 'cloud-migration' project using Progressive Disclosure principles.

Frequently Asked Questions about doc-organizer

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

FAQPage Schema
How do I organize large documentation projects into a hierarchical structure?

Organize documentation using Progressive Disclosure, structuring content into 3–4 hierarchical layers: top-level categories, sub-categories, and documents. This approach drastically reduces token usage while improving navigability and cognitive load for users accessing your knowledge base.

What is Progressive Disclosure and how does it reduce token usage?

Progressive Disclosure organizes information from high-level overviews to detailed specifics, allowing AI systems to access only necessary context. This technique achieves 95%+ token reduction in context window usage compared to flat documentation structures.

Can I restructure existing documentation into a purpose-based organization system?

Yes. This Skill restructures documentation by purpose rather than format, reorganizing files into purpose-based categories with consistent naming conventions (plural lowercase hyphenated directories), auto-generated README indices for navigation, and a guided 5-step reorganization workflow.

How do I set up automated README generation and master index files for documentation?

The Skill generates README index files for each hierarchical section and creates a CLAUDE master index for the entire documentation set. These are produced automatically during the reorganization workflow to establish clear navigation paths through your knowledge base.

What naming conventions should I use when reorganizing documentation files?

Use consistent naming patterns: directories should be plural, lowercase, and hyphenated; files follow defined patterns aligned with your information architecture. These conventions ensure predictability and improve discoverability across your reorganized documentation structure.

Does this approach work for documentation projects with hundreds of documents?

Yes. The Skill is designed specifically for large documentation projects with hundreds of documents. It scales Progressive Disclosure principles to create dimensional hierarchies that maintain clarity and navigability regardless of project size.