documentation-writing SKILL.md skillA
documentation-writing from higoralves/orc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add higoralves/orc/documentation-writing@git:20261020.7a1f356Pins git:20261020.7a1f356 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- higoralves/orc
- Path
orc/skills/documentation-writing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261020.7a1f356, committed Oct 20, 2026
- First version recorded
- Aug 5, 2026
- Size
- 2,703 bytes
- Repository stars
- 7
- License
- MIT
Diátaxis documentation expert.
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
# Diátaxis Documentation Expert You are an expert technical writer specializing in creating high-quality software documentation. Your work is strictly guided by the principles and structure of the Diátaxis Framework (https://diataxis.fr/). ## GUIDING PRINCIPLES 1. **Clarity:** Write in simple, clear, and unambiguous language. 2. **Accuracy:** Verify all information, especially code snippets and technical details, is correct and up-to-date. 3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task. 4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation. ## YOUR TASK: The Four Document Types You will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each: - **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson. - **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe. - **Reference:** Information-oriented, technical descriptions of machinery. A dictionary. - **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion. …
Read the whole file at its exact version.
How to install
mdr add higoralves/orc/documentation-writing@sha256:82ff47ef4852bcb0The line at the top of this page pins the label git:20261020.7a1f356, 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_xnbhlg2clo6nnt4w)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 5, 2026 and Oct 20, 2026, about one every 76 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.7a1f356 latest | 2026-10-20 | 7a1f356 | 2,703 B | A | view · diff |
| git:20260805.600ee50 | 2026-08-05 | 600ee50 | 2,696 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 (2703 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
higoralves/orc · 7 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xnbhlg2clo6nnt4w GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/documentation-writing GET https://markdownregistry.com/api/v1/blob/82ff47ef4852bcb047a7b089c023238097b58f1352a08dbbd93dc9a00eae514e
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.