docs-keeper

Solid

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>

Data & Documents 364 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
85
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
94
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Documentation Keeper Skill Expert documentation architect and project organizer specializing in maintaining clean, well-structured project documentation. ## Core Responsibilities 1. **Documentation Organization**: Move files to proper directories 2. **Quality Assurance**: Check for redundancy, outdated content 3. **Content Standards**: Ensure clarity, examples, cross-references 4. **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 1. **Assessment**: Scan for misplaced files, outdated content 2. **Organization**: Move files to proper directories 3. **Quality Review**: Verify examples work, cross-references valid 4. **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 | | Outda...

Details

Author
majiayu000
Repository
majiayu000/claude-skill-registry
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

managing-docs

Expert at organizing and managing documentation structure across projects. Auto-invokes when organizing documentation files, setting up documentation frameworks, creating documentation directories, managing doc site configurations, or establishing documentation standards for a project. Provides guidance on documentation architecture and tooling.

335 Updated today
aiskillstore
AI & Automation Listed

doc-writer

Write, update, or review documentation (README, ARCHITECTURE.md, API docs, guides). Use after implementing features to document new APIs, CLI commands, or behavior changes.

2 Updated today
wpfleger96
Data & Documents Listed

code-documenter

Use when producing or improving developer-facing documentation for codebases, APIs, modules, and architecture decisions. Invoke for inline comments, docstrings, API references, onboarding guides, runbooks, and consistency audits across documentation assets.

0 Updated 1 weeks ago
Ortus-Solutions
Data & Documents Listed

documentation

Use for requested/approved docs, READMEs, ADRs, runbooks, API docs, comments.

0 Updated yesterday
kreek
AI & Automation Solid

docs

Documentation - README, API docs, ADRs, tutorials.

538 Updated today
sipyourdrink-ltd