technical-writing SKILL.md skillA
technical-writing from lucasheriques/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lucasheriques/pstack/technical-writing@git:20261014.8882c71Pins git:20261014.8882c71 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lucasheriques/pstack
- Path
skills/technical-writing/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261014.8882c71, committed Oct 14, 2026
- First version recorded
- Sep 23, 2026
- Size
- 9,136 bytes
- Repository stars
- 3
- License
- MIT
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
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. 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. Don't invent jargon. Use the words a developer would say out loud: "move", "delete", "a budget that only decreases", not "evacuate", "ratchet", or "endgame". A named pattern is fine when the doc says what it means the first time. Propose a new offender and its replacement as an addition to `unslop`'s abstract-metaphor rule in your reply, with the diff. Don't edit that skill. ## Vary the rhythm …
Read the whole file at its exact version.
How to install
mdr add lucasheriques/pstack/technical-writing@sha256:3dad31e8797c49d1The line at the top of this page pins the label git:20261014.8882c71, 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.
[](https://markdownregistry.com/a/art_fvo4rungdiosxegf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 23, 2026 and Oct 14, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.8882c71 latest | 2026-10-14 | 8882c71 | 9,136 B | A | view · diff |
| git:20261006.3ca5f8f | 2026-10-06 | 3ca5f8f | 9,835 B | A | view · diff |
| git:20260923.11fd787 | 2026-09-23 | 11fd787 | 10,248 B | A | view · diff |
| git:20260923.8a26243 | 2026-09-23 | 8a26243 | 10,205 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9136 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lucasheriques/pstack · 3 stars · license MIT · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fvo4rungdiosxegf GET https://markdownregistry.com/api/v1/resolve?ref=lucasheriques/pstack/technical-writing GET https://markdownregistry.com/api/v1/blob/3dad31e8797c49d1aca4415568f58fc257022940ad0c2f0d6a3e803fb5c7ec9f
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lucasheriques/pstack
Every file in lucasheriques/pstack