content-allocation SKILL.md skillA
content-allocation from akaszubski/autonomous-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add akaszubski/autonomous-dev/content-allocation@git:20260527.8eb022bPins git:20260527.8eb022b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- akaszubski/autonomous-dev
- Path
plugins/autonomous-dev/skills/content-allocation/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260527.8eb022b, committed May 27, 2026
- Size
- 10,244 bytes
- Repository stars
- 34
- License
- none declared
One topic, one home. Routes content to its canonical store (CLAUDE.md, PROJECT.md, MEMORY.md, docs/, memory/) and audits for duplication. TRIGGER when: auditing CLAUDE.md/PROJECT.md/MEMORY.md sizes, deduplicating docs, applying the content-allocation pattern to a new repo, running /align --content. DO NOT TRIGGER when: implementing features, writing tests, routine code edits, debugging.
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
# Content Allocation A methodology for keeping project context lean and unambiguous. Every piece of content has exactly one canonical home; every other appearance is a one-line pointer. ## Methodology: One Topic, One Home **Core rule**: If a piece of content lives in two places, one of them is wrong. The canonical store owns the content; every other location is a one-line pointer to it. Why this matters: - `CLAUDE.md` and `MEMORY.md` are loaded **every turn**. Every line there has compounding cost across the project's lifetime. - Duplication drifts. When the same fact lives in two files, the next edit will update one and leave the other stale. - Readers (humans and assistants) waste tokens hunting through redundant copies for the authoritative version. The pattern works in three moves: 1. **Identify the canonical home** for a topic using the routing table below. 2. **Move the content** to that home. Compress all other appearances to a single-line pointer (`See: docs/RUNBOOK.md`). 3. **Enforce size budgets** so the canonical home does not bloat into a second copy of the wider docs tree. --- ## Routing Table …
Read the whole file at its exact version.
How to install
mdr add akaszubski/autonomous-dev/content-allocation@sha256:a865932671ae692fThe line at the top of this page pins the label git:20260527.8eb022b, 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_tmtuborlfyfhq7wx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 27, 2026.
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 (10244 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
akaszubski/autonomous-dev · 34 stars · license none declared · pushed 2026-10-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_tmtuborlfyfhq7wx GET https://markdownregistry.com/api/v1/resolve?ref=akaszubski/autonomous-dev/content-allocation GET https://markdownregistry.com/api/v1/blob/a865932671ae692f09e7513254aaeb601d3b7a4ca3811d9f3a15335864d04bac
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.