technical-writing SKILL.md skillC
technical-writing from atnexuslab/tightship is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atnexuslab/tightship/technical-writing@git:20261015.8e86e2cPins git:20261015.8e86e2c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 14 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atnexuslab/tightship
- Path
content/skills/technical-writing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261015.8e86e2c, committed Oct 15, 2026
- Size
- 4,966 bytes
- Repository stars
- 4
- License
- MIT
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
+++
name = "technical-writing"
description = "Use when writing or updating a README, a page under docs/, or a runbook — whether the doc should exist, where each fact belongs, and how it stays true as the code moves."
+++
# Technical Writing
A doc is a claim about the code, and it decays the moment the code moves. Write the fewest docs that
answer real questions, put each fact in exactly one place, and prefer the form that cannot go stale.
**Scope.** This skill names criteria, never tools. A repo on this workflow takes its docs structure,
diagrams, and site from `{{skill:project-docs}}`; any other repo takes them from its own `AGENTS.md`.
Project docs live in the **repo** — never only in memory.
## Before writing: should this doc exist?
Every doc is another surface that drifts. It earns its place only when it answers a question that
**nothing else already answers** and someone will actually ask.
Already answered — do not write it down:
- What the code says. A reader who needs the exact behavior reads the code, and prose about it will
disagree with it eventually.
- What a tool prints. Command-line help, a generated schema, a type definition, a config template.
…Read the whole file at its exact version.
How to install
mdr add atnexuslab/tightship/technical-writing@sha256:ed73b1e35161cf36The line at the top of this page pins the label git:20261015.8e86e2c, 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_jqvfhneo55lllxtp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 15, 2026.
Audit of the latest version
- fail: Frontmatter block present
- fail: Frontmatter declares a name
- fail: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4966 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
atnexuslab/tightship · 4 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jqvfhneo55lllxtp GET https://markdownregistry.com/api/v1/resolve?ref=atnexuslab/tightship/technical-writing GET https://markdownregistry.com/api/v1/blob/ed73b1e35161cf36e840bd48b635758b1ae6bc8da6fefeefa5ab74b6d65aabe3
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 atnexuslab/tightship
Every file in atnexuslab/tightship