Agent Skills
› aiming-lab/MetaClaw
› technical-writing-clarity
technical-writing-clarity
GitHub指导如何撰写清晰的技术文档、README和运行手册。遵循目的优先、段落单一、主动语态等原则，提供结构化模板，避免反模式，提升面向工程师的文档质量。
Trigger Scenarios
编写技术文档或README
创建系统说明或运行手册
Install
npx skills add aiming-lab/MetaClaw --skill technical-writing-clarity -g -y
SKILL.md
Frontmatter
{
"name": "technical-writing-clarity",
"category": "communication",
"description": "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."
}
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 scriptnotThe 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:
- Overview (1–2 sentences)
- Prerequisites
- Steps (numbered, imperative)
- Verification / expected output
- Troubleshooting
Anti-patterns: Documenting what without why, outdated examples, walls of text without headers.
Version History
- 922caf3 Current 2026-07-25 11:08
