Write README, API, Runbook, Architecture, and Onboarding documentation.
npx skills add https://github.com/kiryteo/opencode-setup --skill documentation-kiryteo
Please help me install this Agent Skill. Skill: documentation Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/documentation Command: npx skills add https://github.com/kiryteo/opencode-setup --skill documentation-kiryteo
Write clear, maintainable technical documentation for different audiences and purposes.
Create or update a technical document by following the defined document types and structure.
High-intent search queries and answers about installing and using this skill.
Technical documentation for different audiences is written by applying principles like writing for the reader and starting with the lede. This ensures READMEs, API docs, and onboarding guides remain clear and audience-specific.
The best way to structure API documentation and READMEs is by enforcing structured document types and best-practice sections. This approach ensures consistency and usability across end-to-end documentation workflows.
Creating an onboarding guide and runbook involves following defined document types and structure to communicate installation steps and processes. This maintains consistency and shows rather than tells the reader what to do.
Yes, maintaining architecture docs is supported within end-to-end documentation workflows. It enforces structured document types to ensure system designs and onboarding processes are consistently documented and kept current.
You need a runbook for operational procedures and an architecture doc to communicate system designs. Selecting the correct structured document type ensures the content matches its specific technical purpose and audience.
Technical writing lacks consistency when structured document types and best-practice sections are not enforced. Applying principles like linking instead of duplicating ensures READMEs and API documentation remain usable and maintainable.
loongclaw-aiLocate raw Lark OpenAPI endpoints from official markdown documentation.
codethreadGenerate Diátaxis-based technical documentation prompts for vector embedding.
dual-devs0Generate architecture diagrams and analyze system dependencies with Python.
nobe4Enforce plain language and grug principles to produce concise AI responses.
