Documentation
Skill ActiveWrite and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
To help users write and maintain clear, maintainable technical documentation for diverse audiences and purposes, ensuring consistency and up-to-date information.
Features
- Generates README files
- Creates API documentation
- Writes runbooks and architecture documents
- Assists with onboarding guides
- Adheres to documentation principles
Use Cases
- When needing to create a new project README
- When documenting API endpoints and usage
- When developing operational runbooks for procedures
- When drafting architecture overviews or onboarding materials
Non-Goals
- Generating non-technical content
- Replacing in-depth code generation
- Managing project infrastructure
- Providing code review or debugging assistance
Practical Utility
- info:Usage examplesWhile the SKILL.md describes document types and principles, it lacks concrete, end-to-end usage examples demonstrating invocation and observable output for each advertised capability.
- info:Edge casesThe skill identifies different document types and principles but does not explicitly document failure modes, limitations, or recovery steps for edge cases like malformed input or missing dependencies.
Trust
- warning:Issues AttentionIn the last 90 days, 29 issues were opened and 4 were closed, indicating a low closure rate and potentially slow maintainer response.
Installation
First, add the marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install engineering@knowledge-work-pluginsQuality Score
Trust Signals
Similar Extensions
Documentation Engineer
100Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Technical Blog Writing
99Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical content
Teach Guidance
100Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
External Context
100Invoke parallel document-specialist agents for external web searches and documentation lookup
Deepinit
100Deep codebase initialization with hierarchical AGENTS.md documentation