Write a document a tired engineer understands on the first read. Use for /technical-writing, or when writing or reviewing a doc, RFC, README, PR description, or commit message. A chat reply stays with diu.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Technical writing
Write so a tired engineer understands on the first read. Apply all four layers.
`diu` owns a chat reply. This skill owns a document: a README, an RFC, a PR body, or a commit message. Type `/technical-writing` to run it.
Three rules sit above the layers:
- **Cut every word that does no work.** If the sentence survives without a word, the word goes. "In order to" is "to". "It is important to note that" is nothing.
- **Use the short, everyday word.** "Use", not "utilize". "Help", not "facilitate". "Do", not "perform". A long word has to buy its length with precision.
- **When a rule makes a sentence worse, fix the sentence another way or leave it alone.** A sentence that follows every rule and sounds like a machine wrote it has failed.
The codebase is the word list. Write the real symbol, file, flag, or command name, not a synonym or a description of it.
…
The line at the top of this page pins the label git:20261022.2eaf2ab, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_xl6hm3woqkvwfpif
GET https://markdownregistry.com/api/v1/resolve?ref=edbertchan/catstack/technical-writing
GET https://markdownregistry.com/api/v1/blob/607d88c5b76167970c3cbf303c113800642837ab00f3206d92de599d692aac27
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
edbertchan/catstack · corpus/skills/cat-mode/SKILL.md · Edbert's personal working conventions, mined from real session history across his projects. Use when Edbert asks to…
edbertchan/catstack · corpus/skills/principle-assert-invariants-not-last-bug/SKILL.md · Apply after a bug ships past review or a passing grade/check: assert the general class of failure instead of patching…
edbertchan/catstack · corpus/skills/principle-bind-to-named-inventory/SKILL.md · Apply after an audit, scoring review, or a request for a "real classifier" / "less arbitrary weights" when existing…
edbertchan/catstack · corpus/skills/principle-build-the-lever/SKILL.md · Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or…
edbertchan/catstack · corpus/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
edbertchan/catstack · corpus/skills/principle-experience-first/SKILL.md · Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship…
edbertchan/catstack · corpus/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach…
edbertchan/catstack · corpus/skills/principle-flag-your-own-corrections/SKILL.md · Apply whenever you are about to admit fault in any wording — a fact, number, claim, or check you already stated turns…
edbertchan/catstack · corpus/skills/principle-generalize-from-rejection/SKILL.md · Apply when a mechanical gate — a lint, validator, blocked-command guard, or CI check — rejects your output for the same…
openhands/extensions · skills/technical-writing/SKILL.md · Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering…
nahid-sparktales/agent-dispatcher · skills/knowledge/technical-writing/SKILL.md · Write or repair documentation that stays true to the system it describes — README, setup guide, how-to, API reference…
korallis/agent-stack · skills/technical-writing/SKILL.md · How to write docs, SPECs, READMEs, runbooks, PR descriptions and commit messages that a tired engineer understands on…
toongri/oh-my-toong-playground · skills/technical-writing/SKILL.md · Use when reviewing, improving, or writing technical documentation in Korean. Triggers include "문서 리뷰", "테크니컬 라이팅", "기술…
