
Quality Documentation Manager
Structure how your agent maintains reference assets and quality documentation alongside shipped features.
Overview
Quality Documentation Manager is an agent skill most often used in Build (also Ship) that templates reference docs and asset layout for maintainable product documentation.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill quality-documentation-managerWhat is this skill?
- Separates context-loaded SKILL content from binary assets (templates, images, fonts) not meant for model context
- Documents common asset types: `.pptx`, `.docx`, boilerplate dirs, `.csv`, `.json`, icons, and starter code
- Includes a reference-doc scaffold pattern (`references/`) for deep API or workflow guides
- Aligns with Claude Code Templates skill packaging conventions for davila7-style repos
Adoption & trust: 748 installs on skills.sh; 27.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent skill repo mixes huge assets with SKILL.md and has no clear place for deep reference material or quality doc standards.
Who is it for?
Builders scaffolding a new Claude skill or docs package who need opinionated structure before writing real reference markdown.
Skip if: Anyone expecting an automated doc linter, MkDocs generator, or ready-made quality rubric—the shipped readme is placeholder scaffolding.
When should I use this skill?
User is scaffolding documentation assets, reference folders, or quality doc layout inside a Claude Code Templates skill repo.
What do I get? / Deliverables
You get a documented folder pattern for assets versus references so outputs stay consistent and context stays lean as you flesh in real content.
- Documented asset and reference directory conventions
- Placeholder files to swap for real templates
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Documentation quality gates belong where specs and references are authored—primarily Build before reviews and release. The skill template targets reference docs, asset bundles, and placeholders for PM-style documentation artifacts under `docs`.
Where it fits
Lay out `references/communication.md` and image assets before writing API guides for your SaaS.
Attach status-update templates as `.docx` assets the agent fills without loading binaries into chat.
Point reviewers to centralized reference docs instead of scattered SKILL fragments.
How it compares
Use as a packaging starter, not as a substitute for a dedicated documentation generator or static-site skill.
Common Questions / FAQ
Who is quality-documentation-manager for?
Solo developers and template authors setting up Claude Code skills who want asset versus reference separation before writing real documentation.
When should I use quality-documentation-manager?
In Build while structuring `references/` and asset folders; in Ship during review when you need a checklist-oriented doc program (after you replace placeholders).
Is quality-documentation-manager safe to install?
It is primarily text scaffolding—check the Security Audits panel on this page and review any assets you add locally.
SKILL.md
READMESKILL.md - Quality Documentation Manager
# Example Asset File This placeholder represents where asset files would be stored. Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed. Asset files are NOT intended to be loaded into context, but rather used within the output Claude produces. Example asset files from other skills: - Brand guidelines: logo.png, slides_template.pptx - Frontend builder: hello-world/ directory with HTML/React boilerplate - Typography: custom-font.ttf, font-family.woff2 - Data: sample_data.csv, test_dataset.json ## Common Asset Types - Templates: .pptx, .docx, boilerplate directories - Images: .png, .jpg, .svg, .gif - Fonts: .ttf, .otf, .woff, .woff2 - Boilerplate code: Project directories, starter files - Icons: .ico, .svg - Data files: .csv, .json, .xml, .yaml Note: This is a text placeholder. Actual assets can be any file type. # Reference Documentation for Quality Documentation Manager This is a placeholder for detailed reference documentation. Replace with actual reference content or delete if not needed. Example real reference docs from other skills: - product-management/references/communication.md - Comprehensive guide for status updates - product-management/references/context_building.md - Deep-dive on gathering context - bigquery/references/ - API references and query examples ## When Reference Docs Are Useful Reference docs are ideal for: - Comprehensive API documentation - Detailed workflow guides - Complex multi-step processes - Information too lengthy for main SKILL.md - Content that's only needed for specific use cases ## Structure Suggestions ### API Reference Example - Overview - Authentication - Endpoints with examples - Error codes - Rate limits ### Workflow Guide Example - Prerequisites - Step-by-step instructions - Common patterns - Troubleshooting - Best practices #!/usr/bin/env python3 """ Example helper script for quality-documentation-manager This is a placeholder script that can be executed directly. Replace with actual implementation or delete if not needed. Example real scripts from other skills: - pdf/scripts/fill_fillable_fields.py - Fills PDF form fields - pdf/scripts/convert_pdf_to_images.py - Converts PDF pages to images """ def main(): print("This is an example script for quality-documentation-manager") # TODO: Add actual script logic here # This could be data processing, file conversion, API calls, etc. if __name__ == "__main__": main() --- name: quality-documentation-manager description: Senior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory documentation oversight. Use for document control system implementation, regulatory document review, change management, and documentation compliance verification. --- # Senior Quality Documentation Manager Expert-level quality documentation management with comprehensive document control system design, regulatory documentation oversight, change management, and configuration control for medical device organizations. ## Core Documentation Management Competencies ### 1. Document Control System Design (ISO 13485 Clause 4.2.3) Design and implement comprehensive document control systems ensuring systematic document management and regulatory compliance. **Document Control System Framework:** ``` DOCUMENT CONTROL SYSTEM ARCHITECTURE ├── Document Classification and Structure │ ├── Document type taxonomy and hierarchy │ ├── Document numbering and identification │ ├── Version control and revision management │ └── Document status and lifecycle tracking ├── Document Creation and Approval │ ├── Document templates and standardization │ ├── Review and approval workflows │ ├── Author and reviewer role assignment │ └── Quality assurance and validation ├── Document Distribution and Access │ ├── Controlled distribution management │ ├── Access pe