sota-docs-workflow SKILL.md skillA
sota-docs-workflow from martinholovsky/sota-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinholovsky/sota-skills/sota-docs-workflow@git:20261024.8dd2b0aPins git:20261024.8dd2b0a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinholovsky/sota-skills
- Path
skills/sota-docs-workflow/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261024.8dd2b0a, committed Oct 24, 2026
- First version recorded
- Jun 17, 2026
- Size
- 11,767 bytes
- Repository stars
- 26
- License
- CC-BY-4.0
State-of-the-art documentation and engineering-collaboration guidance (2026) covering documentation architecture (Diátaxis, docs-as-code, READMEs, runbooks, onboarding, AI-readable docs), API/reference docs and changelogs, and the team workflow around code: pull requests, code review conduct, commit discipline, branching, and releases. Use when writing or structuring any documentation AND when auditing docs quality, and when designing or auditing collaboration workflow. Not for in-product UI…
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
# SOTA Docs & Engineering Workflow ## Purpose Expert-level rules for the artifacts around the code: documentation (structure, reference, freshness, runbooks) and the collaboration workflow (PRs, review, commits, releases). These are the highest-leverage, lowest-glamour practices — review latency and doc decay quietly dominate team throughput. Rules are imperative with rationale and good/bad examples; every rules file ends with an audit checklist. Load only the files relevant to the task via the index below. Boundaries: ADR practice lives in [`sota-architecture`](../sota-architecture/SKILL.md); API contract design in [`sota-api-design`](../sota-api-design/SKILL.md); tag signing/provenance and CI supply chain in [`sota-devsecops`](../sota-devsecops/SKILL.md). This skill references them rather than repeating them. ## BUILD mode When creating docs or setting up workflow: 1. **Classify before writing.** Every doc is exactly one Diátaxis mode (tutorial / how-to / reference / explanation) and is titled accordingly; mixed-mode pages are the defect to design out ([`rules/01`](rules/01-documentation-architecture.md) §1). …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-docs-workflow@sha256:dff587dbf9c75ca7The line at the top of this page pins the label git:20261024.8dd2b0a, 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_d2eymgbfsmr6zluz)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 17, 2026 and Oct 24, 2026, about one every 22 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.8dd2b0a latest | 2026-10-24 | 8dd2b0a | 11,767 B | A | view · diff |
| git:20261012.ae1b29b | 2026-10-12 | ae1b29b | 11,526 B | A | view · diff |
| git:20260728.31613f4 | 2026-07-28 | 31613f4 | 10,115 B | A | view · diff |
| git:20260716.c471ba1 | 2026-07-16 | c471ba1 | 9,818 B | A | view · diff |
| git:20260716.e4afc80 | 2026-07-16 | e4afc80 | 9,449 B | A | view · diff |
| git:20260626.8c3a035 | 2026-06-26 | 8c3a035 | 9,336 B | A | view · diff |
| git:20260617.c5d2c7b | 2026-06-17 | c5d2c7b | 8,782 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 (11767 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
martinholovsky/sota-skills · 26 stars · license CC-BY-4.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d2eymgbfsmr6zluz GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-docs-workflow GET https://markdownregistry.com/api/v1/blob/dff587dbf9c75ca7a59e204d0d3272fe58412962df5ebe1fcbfd4793028dbf6d
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.