brainharness-docs SKILL.md skillA
brainharness-docs from zning1994/brainharness-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zning1994/brainharness-docs/brainharness-docs@v1.2.1Pins v1.2.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zning1994/brainharness-docs
- Path
SKILL.md- Versions recorded
- 4
- Latest version
- v1.2.1, committed Oct 3, 2026
- First version recorded
- Apr 6, 2026
- Size
- 12,634 bytes
- Repository stars
- 2
- License
- MIT
Organize project documentation by size, audience, and freshness. Trigger when setting up docs for a new project, restructuring existing documentation, slimming a bloated CLAUDE.md/AGENTS.md, deciding where a doc should live, or on doc best practices questions. Also trigger when CLAUDE.md exceeds ~250 lines or docs are duplicated across files. Triggers on: organize docs, reorganize documentation, slim CLAUDE.md, AGENTS.md too long, where to put docs, docs structure, doc best practices, set up…
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
# BrainHarness Docs A practical guide for organizing project documentation so that every fact has one home, AI agents load only what they need, and humans can find things without grep. ## Why This Matters Poor doc organization creates three problems that compound over time: 1. **Drift** — the same fact copied into 3 files eventually becomes 3 different "truths" 2. **Context waste** — a 2000-line CLAUDE.md burns AI tokens on every conversation, most of it irrelevant 3. **Lost docs** — flat directories with 20+ files make everything hard to find The fix is simple: organize by who reads it and whether it stays current. ## Step 0: Root-Level Noise Audit Before touching docs, clean non-documentation clutter from the project root. Root-level noise (screenshots, recordings, debug logs, AI chat exports) is often the biggest source of visual chaos — and it has nothing to do with documentation structure. Run `ls | wc -l` and capture the count. Then identify and relocate: | What to look for | Where it goes | |-----------------|---------------| | Screenshots, recordings (`.png`, `.mov`, `.mp4`) | `archive/media/` or `screenshots/` if curated | …
Read the whole file at its exact version.
How to install
mdr add zning1994/brainharness-docs/brainharness-docs@sha256:8971dc8f01bfc751The line at the top of this page pins the label v1.2.1, 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_n4pvkuqoktbuflzc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 6, 2026 and Oct 3, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.1 latest | 2026-10-03 | 84d6291 | 12,634 B | A | view · diff |
| v1.2.0 | 2026-10-03 | 43e7f13 | 12,634 B | A | view · diff |
| v1.1.0 | 2026-04-07 | 98a63e8 | 12,643 B | A | view · diff |
| v1.0.0 | 2026-04-06 | d0ede83 | 9,155 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 (12634 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
zning1994/brainharness-docs · 2 stars · license MIT · pushed 2026-10-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n4pvkuqoktbuflzc GET https://markdownregistry.com/api/v1/resolve?ref=zning1994/brainharness-docs/brainharness-docs GET https://markdownregistry.com/api/v1/blob/8971dc8f01bfc751df19189626ed4f2ae56ffea8a82faaa372b0657c30008103
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 zning1994/brainharness-docs
Every file in zning1994/brainharness-docs