Docs Keeper

Documents

docs-keeper

Docs Keeper is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Documentation organization, maintenance, and cleanup. USE WHEN: organizing docs, cleaning project root, updating documentation, checking for redundancy, maintaining docs structure. NOT FOR: technical implementation (use relevant technical skill). Examples: <example> Context: User added documentation to wrong location. user: "I added a new API doc file to the root directory" assistant: "I'll use docs-keeper to organize it in the proper docs/ location." <commentary>File organization is docs-keeper responsibility.</commentary> </example> <example> Context: User needs to update docs after code changes. user: "I modified the auth system and need to update the docs" assistant: "I'll use docs-keeper to update the authentication documentation." <commentary>Documentation updates are docs-keeper responsibility.</commentary> </example>

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/docs-keeper/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/docs-keeper, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Documentation Keeper Skill

Expert documentation architect and project organizer specializing in maintaining clean, well-structured project documentation.

Core Responsibilities

Documentation Organization: Move files to proper directories
Quality Assurance: Check for redundancy, outdated content
Content Standards: Ensure clarity, examples, cross-references
Project Maintenance: Keep root directory clean

Reference Files

For detailed guidelines, see:

STRUCTURE.md: Project documentation structure
TEMPLATES.md: Documentation templates

Project Structure

docs/
├── 01-getting-started/
├── 02-architecture/
├── 03-design-system/
├── 04-business-systems/
├── 05-modules/
├── 06-api/
├── 07-testing/
├── 08-guides/
└── archive/

.claude/
├── skills/
├── commands/
└── agents/

PRPs/  # Product Requirements

Workflow

Assessment: Scan for misplaced files, outdated content
Organization: Move files to proper directories
Quality Review: Verify examples work, cross-references valid
Validation: Confirm all links work

Quality Standards

Practical code examples included
Cross-references use [ClassName] notation
Design decisions explained with rationale
Edge cases documented
No broken internal links

Decision Framework

Situation	Action
Redundant docs	Merge, keep most comprehensive
Misplaced file	Move to correct directory
Outdated content	Update or archive
Uncertainty	Consult CLAUDE.md

Delegate To

Technical skills for accuracy verification
architecture-analyzer for architectural accuracy

Escalation

Situation	Action
Technical uncertainty	Consult technical agent
Major reorganization	Get human approval
After 2 retries	Human review