Write or edit technical documents, RFCs, and PR descriptions for a clear audience and purpose.
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 for the reader's task and background. Follow the repository's document template and terminology.
Choose a structure that serves the purpose: a tutorial teaches through a worked example, a how-to solves a task, reference supports lookup, and explanation develops understanding. Combine or link sections when that helps the reader; a short PR description does not need this classification exercise.
- Lead with the result, problem, or action the reader needs.
- Use real symbols, commands, and paths. Keep names consistent.
- Give instructions as commands, with relevant conditions before the action.
- Prefer concrete language and active verbs. Preserve necessary qualifications.
- Use examples, tables, or diagrams only when they clarify something prose would make harder.
- Match code formatting to the project. Do not impose global punctuation, indentation, or sentence-length rules.
- State the validation actually performed and the limits of the evidence.
Edit directly for clarity. No mandatory second skill pass or expansion of a shared banned-word list is needed.
The line at the top of this page pins the label git:20260907.b1269d9, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1273 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
GitHub
shiwenbin1617/pstack · 4 stars · license a license file GitHub does not identify · pushed 2026-09-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rvohc7liu2236rdy
GET https://markdownregistry.com/api/v1/resolve?ref=shiwenbin1617/pstack/technical-writing
GET https://markdownregistry.com/api/v1/blob/1b29da706ae581e71374ad9f95a767ed9681d49bf36c08555971da030da02aad
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.
shiwenbin1617/pstack · adapters/claude-code/overrides/setup-pstack/SKILL.md · Configure which Claude Code models pstack uses per role. Use for /setup-pstack or requests to change pstack model…
shiwenbin1617/pstack · adapters/codex/overrides/setup-pstack/SKILL.md · Configure optional per-role model preferences for pstack on Codex. Use for $setup-pstack or requests to change pstack…
shiwenbin1617/pstack · automations/benny/skills/reproduce-and-fix-issues/SKILL.md · Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft…
shiwenbin1617/pstack · automations/benny/skills/setup-benny/SKILL.md · Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker…
shiwenbin1617/pstack · skills/architect/SKILL.md · Design types, interfaces, and module ownership for a requested architectural change or an unresolved design choice.
shiwenbin1617/pstack · skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
shiwenbin1617/pstack · skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
shiwenbin1617/pstack · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
shiwenbin1617/pstack · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
rsmdt/the-startup · plugins/team/skills/development/technical-writing/SKILL.md · Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use…
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…
