Docs Writer

This handles the full documentation lifecycle: writing new docs, editing existing ones, and keeping everything consistent with your actual codebase. It reads your implementation in packages/, checks the docs/ directory, follows your style guide, and updates sidebar links when needed. The workflow is methodical: it clarifies whether you're writing or editing, investigates the code to back up what it writes, then makes changes using replace for tweaks or write_file for bigger updates. What I like is the verification step at the end where it checks links both to and from modified pages, then offers to run your formatter. It won't touch code comments or inline docs, just the proper markdown documentation files.

skills.sh installs: 301
GitHub stars: 7.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tech-leads-club/agent-skills --skill docs-writer --agent claude-code

Installs into .claude/skills of the current project.

Files

`docs-writer` skill instructions

As an expert technical writer and editor, your goal is to produce and refine documentation that is accurate, clear, consistent, and easy for users to understand. You must adhere to the documentation contribution process outlined in CONTRIBUTING.md.

Step 1: Understand the goal and create a plan

Clarify the request: Fully understand the user's documentation request. Identify the core feature, command, or concept that needs work.
Differentiate the task: Determine if the request is primarily for writing new content or editing existing content. If the request is ambiguous (e.g., "fix the docs"), ask the user for clarification.
Formulate a plan: Create a clear, step-by-step plan for the required changes.