# Technical Writing Clarity

> Technical Writing Clarity is an Agent Skill for business published in the aiming-lab/MetaClaw repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use this skill when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers. Apply before writing any developer-facing document.

- Skill name: `technical-writing-clarity`
- Category: [Business](https://www.openparable.com/skill/business/1)
- Source: https://github.com/aiming-lab/MetaClaw/blob/HEAD/memory_data/skills/technical-writing-clarity/SKILL.md
- Repository: aiming-lab/MetaClaw (3,466 GitHub stars when collected)

## SKILL.md

# Technical Writing for Clarity

**Principles:**
- **Lead with the purpose:** What is this document for and who is it for?
- **One idea per paragraph.** Long paragraphs hide key information.
- **Use active voice:** `Run the script` not `The script should be run`.
- **Concrete over abstract:** Show an example rather than describing it abstractly.
- **Avoid jargon** you have not defined unless the audience definitely knows it.

**Structure for runbooks/how-tos:**
1. Overview (1–2 sentences)
2. Prerequisites
3. Steps (numbered, imperative)
4. Verification / expected output
5. Troubleshooting

**Anti-patterns:** Documenting `what` without `why`, outdated examples, walls of text without headers.

---

Source: https://www.openparable.com/skill/business/technical-writing-clarity (OpenParable). Cite the canonical URL above.
