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
Use this skill when the deliverable is **internal technical documentation for builders and operators**.
`technical-writing` is the documentation-cluster anchor for:
- technical specs
- product requirements documents (PRDs)
- architecture docs
- ADRs / decision records
- runbooks and incident procedures
- rollout / rollback / migration guides
- developer-facing implementation or maintenance guides
## When to use this skill
- A team needs a technical spec before implementation starts
- A team needs a PRD for product/feature requirements before design or implementation
- An engineer needs an architecture document or ADR that records trade-offs and decisions
- Ops needs a runbook, rollback guide, or incident response procedure
- A migration or rollout needs a durable written path with validation and rollback notes
- A developer-facing internal guide needs to explain how a system works and how to work on it safely
## When not to use this skill
The lane is *internal* documentation. Say so and hand back when the real job is:
- **Published API, SDK, OpenAPI or developer-portal content** — an external
reference surface with its own versioning and consumers.
…
The line at the top of this page pins the label v2.1.0, 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_y3uen4x3a3pf4rno
GET https://markdownregistry.com/api/v1/resolve?ref=bjornmelin/dev-skills/technical-writing
GET https://markdownregistry.com/api/v1/blob/b272270e6a682358267ac1f00c47efb7073b8fcf4ae5bc8eccd827c5bed7b391
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.
bjornmelin/dev-skills · archive/skills/browser-workbench-setup/SKILL.md · Set up browser automation and UI QA for a new repository using playwright-interactive as the primary interactive tool…
bjornmelin/dev-skills · archive/skills/bun-audit/SKILL.md · Shared Bun audit/remediation router. Use when auditing a repo for Bun-first correctness, explaining findings, listing…
bjornmelin/dev-skills · archive/skills/managing-tech-debt/SKILL.md · Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring…
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…
