technical-writer

Generate developer documentation with validated code examples and link checks.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill technical-writer-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-writer
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/technical-writer
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill technical-writer-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Reduces friction and errors caused by unclear, inconsistent, or outdated developer documentation so teams can onboard faster and operate reliably. It helps ensure code examples work, architecture decisions are recorded, and runbooks are actionable during incidents.

Core Features & Use Cases

  • Templates for common doc types: README, API reference, ADRs, and runbooks to standardize output and speed authoring.
  • Quality validation: A validation script and checklist to catch broken links, missing sections, and documentation anti-patterns.
  • Diátaxis-aligned guidance: Helps choose the right doc type (tutorial, how-to, explanation, reference) and provides troubleshooting and example-checking best practices.

Quick Start

Ask the technical-writer skill to draft a project README using the readme-template.md and then run the validation script to check examples and links.

Frequently Asked Questions about technical-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create clear and maintainable developer documentation?

To create clear developer documentation, use standardized templates for README files, API references, and runbooks, then apply a validation script to catch broken links and verify executable code examples for accuracy.

What is the Diátaxis framework and how does it structure technical documentation?

The Diátaxis framework structures technical documentation into four types: tutorials, how-to guides, explanation, and reference. Aligning docs with this structure ensures users find the right information for their specific learning or operational needs.

How do I write an actionable runbook for incident response?

Write an actionable runbook by using standardized templates that ensure operational reliability during incidents. A validation script then checks the runbook for missing sections and verifies that troubleshooting code examples are executable.

What's the best way to validate links and code examples in README files?

The best way to validate links and code examples in README files is to run an automated validation script against your markdown templates. This catches broken links, identifies missing sections, and performs basic executable validation for documentation quality.

How do I record architecture decisions for engineering teams?

Record architecture decisions by using an ADR template. This standardizes the documentation of architectural choices, ensuring decisions are consistently captured and easily referenced by engineering and operations teams.

Does this documentation tool require any specific dependencies or environments?

No specific dependencies are required to draft documentation. The process uses markdown templates and a validation script, ensuring you can standardize output and check documentation anti-patterns in any standard developer environment.