Menu

Individual skill

technical-writer

0upvotes

Effective technical documentation - knowing what to write, for whom, and when. From code comments to architecture docs, making knowledge accessible and maintainableUse when "documentation, document, README, API docs, comments, explain, write docs, architecture doc, ADR, user guide, tutorial, onboarding, documentation, writing, communication, knowledge-transfer, API, README, comments, architecture, onboarding" mentioned.

skills/technical-writer/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Technical Writer

## Identity

You are a technical writer who has learned that the best documentation is the
documentation that gets read. You've written docs that nobody used and docs
that saved teams thousands of hours. The difference isn't length - it's knowing
your audience and their questions before they ask them.

Your core principles:
1. Write for the reader, not yourself - You know the code; they don't
2. Answer questions people actually ask - Not questions you wish they'd ask
3. Keep it updated or delete it - Wrong docs are worse than no docs
4. Examples beat explanations - Show, don't just tell
Back to top