documentation-librarian

Name: documentation-librarian
Availability: InStock
Author: Grig

Audit documentation directories and restructure files into ontological taxonomies.

4|Updated Dec 7, 2025

Search Tags:#documentation #audit #library #organization #information architecture #taxonomy

Ready to run

npx skills add https://github.com/grigb/gas-prompt-library --skill documentation-librarian-grigb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-librarian
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-documentation-librarian
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill documentation-librarian-grigb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the chaos of unorganized documentation directories by providing a structured, safe, and systematic approach to auditing, categorizing, and restructuring technical content.

Core Features & Use Cases

Ontological Auditing: Scans directories to identify document types, duplications, and outdated content.
Safe Restructuring: Proposes and implements organizational changes using an archival-first approach that prevents data loss.
Index Management: Automatically creates and maintains INDEX.md files to ensure documentation remains discoverable.
Use Case: Use this agent to clean up a legacy project folder containing hundreds of mixed markdown files by categorizing them into architecture, API, and user guide sections.

Quick Start

Use the documentation-librarian skill to audit the current directory and propose a new organizational structure for all markdown files.

Frequently Asked Questions about documentation-librarian

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

FAQPage Schema

How do I audit and reorganize a chaotic documentation directory?▼

To audit a documentation directory, the skill scans project folders to identify document types and duplications, then proposes an ontological taxonomy to categorize files into clear, logical sections.

What is the safest way to restructure legacy project documentation without losing files?▼

The safest way to restructure documentation is using an archival-first approach that archives redundant or outdated files without permanent deletion, ensuring original information integrity.

How do I automatically generate and maintain indexes for a markdown documentation library?▼

You can maintain a documentation library by automatically creating and updating INDEX.md files within the directory, ensuring all markdown content remains organized and discoverable.

Can I categorize mixed markdown files into architecture, API, and user guide sections automatically?▼

Yes, you can categorize mixed markdown files by analyzing the directory content and proposing a user-approved restructuring plan that sorts files into architecture, API, and user guide sections.

Does the documentation restructuring process require user approval before applying changes?▼

Yes, the restructuring process requires strict adherence to user-approved plans, meaning it proposes organizational changes and archival actions before applying them to the directory.