writing-for-a-technical-audience SKILL.md skillA
writing-for-a-technical-audience from ed3dai/ed3d-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ed3dai/ed3d-plugins/writing-for-a-technical-audience@git:20260204.611bfd1Pins git:20260204.611bfd1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ed3dai/ed3d-plugins
- Path
plugins/ed3d-house-style/skills/writing-for-a-technical-audience/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260204.611bfd1, committed Feb 4, 2026
- First version recorded
- Jan 15, 2026
- Size
- 15,448 bytes
- Repository stars
- 253
- License
- none declared
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity.
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
# Writing for a Technical Audience ## Overview **Core principle:** Technical writing must be clear, concise, and authentic. Clarity and technical depth are not opposites - you can have both. Avoid AI writing patterns that make content feel robotic or inauthentic.  **Why this matters:** Developers value their time. Clear documentation builds trust. AI-like writing patterns (identified through research) make content feel generic and untrustworthy. Technical depth without clarity frustrates users. Clarity without depth leaves them stuck. ## When to Use **Use this skill when:** - Writing API documentation or references - Creating guides, tutorials, or how-to content - Documenting code, features, or architecture - Writing technical blog posts or articles - Reviewing technical content for clarity **Trigger symptoms:** - "Does this sound too robotic?" - Writing feels formal or stiff - Using phrases like "delve into" or "leverage" - Explaining obvious things instead of getting to the point - Uncertain if content is clear enough ## The Three Pillars ### 1. Clarity Developers should understand on first read. No re-reading required. **Techniques:** …
Read the whole file at its exact version.
How to install
mdr add ed3dai/ed3d-plugins/writing-for-a-technical-audience@sha256:ed06d8e2b8607585The line at the top of this page pins the label git:20260204.611bfd1, 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_ijazuqfdrqe7txa4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jan 15, 2026 and Feb 4, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260204.611bfd1 latest | 2026-02-04 | 611bfd1 | 15,448 B | A | view · diff |
| git:20260115.cf17c55 | 2026-01-15 | cf17c55 | 15,426 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 (15448 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
ed3dai/ed3d-plugins · 253 stars · license none declared · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ijazuqfdrqe7txa4 GET https://markdownregistry.com/api/v1/resolve?ref=ed3dai/ed3d-plugins/writing-for-a-technical-audience GET https://markdownregistry.com/api/v1/blob/ed06d8e2b86075858e473935fc879265ac97a2a62e01309ebb564cf575543c56
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.