technical-writer SKILL.md skillA
technical-writer from widnyana/eyay-toolkits is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add widnyana/eyay-toolkits/technical-writer@git:20260829.6d9d2bbPins git:20260829.6d9d2bb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- widnyana/eyay-toolkits
- Path
plugins/prose-engineers/skills/technical-writer/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260829.6d9d2bb, committed Aug 29, 2026
- First version recorded
- May 10, 2026
- Size
- 12,248 bytes
- Repository stars
- 8
- License
- MIT
This skill should be used when the user asks to "write a blog post", "draft a postmortem", "document this process", "write an incident writeup", "review this article", "write API docs", "write a how-to guide", "compare these two tools", "write up this feature", "make this scannable", "restructure this draft", or "nobody finishes reading this". Produces technical writing that is problem-first, concrete, and humble: real numbers instead of adjectives, real incidents instead of invented…
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
# Approachable Technical Writer Writing for people who ship things. They don't need theory or marketing language — they need to know what matters, why it breaks, and how to fix it. They also want the human part: why this was discovered, what it cost, where the traps are. ## Workflow 1. **Find the problem.** Before drafting, identify what breaks or costs something if the reader ignores this. If that can't be named, stop and ask the user — a piece without a problem has no opening. 2. **Collect the real material.** Actual numbers, actual code, actual incidents. Ask the user for specifics rather than inventing plausible ones. Missing evidence is a gap to acknowledge, not to fill. 3. **Pick a pattern.** Load `references/patterns.md` and choose the template matching the piece type (default, how-to, review, explanation, postmortem). 4. **Draft in plain text.** Structure and words first; Markdown, HTML, or vault formatting later. 5. **Run the checklist.** Every item at the bottom of this file, before handing back. Default to public-facing mode. Switch to internal mode when the user says "internal" or "for the team". ## Core principles ### 1. Problem first …
Read the whole file at its exact version.
How to install
mdr add widnyana/eyay-toolkits/technical-writer@sha256:a733c40be9303755The line at the top of this page pins the label git:20260829.6d9d2bb, 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_g7bdqdujbzki2yfh)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 10, 2026 and Aug 29, 2026, about one every 111 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260829.6d9d2bb latest | 2026-08-29 | 6d9d2bb | 12,248 B | A | view · diff |
| git:20260510.b02852b | 2026-05-10 | b02852b | 12,672 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 (12248 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
widnyana/eyay-toolkits · 8 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g7bdqdujbzki2yfh GET https://markdownregistry.com/api/v1/resolve?ref=widnyana/eyay-toolkits/technical-writer GET https://markdownregistry.com/api/v1/blob/a733c40be930375559b9fe3840347484de55f7a3ef62e3d76619cb24b49d1ee5
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 widnyana/eyay-toolkits
Every file in widnyana/eyay-toolkits