memory-tidy SKILL.md skillA

memory-tidy from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add atman-33/workhub/memory-tidy@git:20260929.8af6e2e

Pins git:20260929.8af6e2e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: atman-33/workhub
Path: plugins/memory/skills/memory-tidy/SKILL.md
Versions recorded: 5
Latest version: git:20260929.8af6e2e, committed Sep 29, 2026
First version recorded: Sep 17, 2026
Size: 5,302 bytes
Repository stars: 3
License: MIT

Keep memory small enough to stay useful - report which caps are over, propose merges, split bloated notes, archive what is finished, and connect orphans. Use when memory-doctor or the session brief reports a cap, when memory feels noisy, or on a periodic review.

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

# memory-tidy — forgetting, on purpose

Promotion without forgetting just makes a bigger pile. `identity/` is read in
full on every session, so its size is not a matter of taste: a note nobody can
read in one pass stops being read at all, and then the judgement it holds stops
applying.

So the layers have caps, and reaching one is the signal to consolidate. The cap
is the mechanism — not a tidiness rule, and not a number to raise when it gets
inconvenient. It already works: `memory/identity/decision-policy.md` has held to "50
entries, 3 lines each, a fifty-first arrives by merging or dropping one" and it
is the one part of the harness that has never bloated. What the number cannot
tell you is which entries still earn their place — for that, step 1 also asks
which ones nobody has cited.

## What this may do on its own

| Action | Do it |
|---|---|
| **Archive** a finished or superseded note | Without asking. Reversible, and it stays in the graph |
| **Add a missing link** between two notes | Without asking |
| **Merge** two notes, or rewrite one | Propose it. Show what would be lost |
| Change anything in **`identity/`** | Propose it. Always |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add atman-33/workhub/memory-tidy@sha256:074ec23a8d3bca58

The line at the top of this page pins the label git:20260929.8af6e2e, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_gcw2cqkve2kig2xu.svg)](https://markdownregistry.com/a/art_gcw2cqkve2kig2xu)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Sep 17, 2026 and Sep 29, 2026, about one every 3 days.

version	committed	commit	size	audit
git:20260929.8af6e2e latest	2026-09-29	8af6e2e	5,302 B	A	view · diff
git:20260929.34df0e5	2026-09-29	34df0e5	4,906 B	A	view · diff
git:20260919.cadb034	2026-09-19	cadb034	4,089 B	A	view · diff
git:20260917.68a9029	2026-09-17	68a9029	4,012 B	A	view · diff
git:20260917.005d18d	2026-09-17	005d18d	4,004 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5302 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

GitHub

atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_gcw2cqkve2kig2xu
GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/memory-tidy
GET https://markdownregistry.com/api/v1/blob/074ec23a8d3bca58361a8c6f30a2131ad2c726de09182558b11b6b614adc7fdb

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 atman-33/workhub

CLAUDE.md CLAUDE.md file

atman-33/workhub · CLAUDE.md

git:20260929.5a11e52 · audit A · 3 stars

AGENTS.md@demo-vault AGENTS.md file

atman-33/workhub · demo-vault/AGENTS.md

git:20260830.27fbb5d · audit A · 3 stars

CLAUDE.md@demo-vault CLAUDE.md file

atman-33/workhub · demo-vault/CLAUDE.md

git:20260930.4c9347d · audit A · 3 stars

handoff-go SKILL.md skill

atman-33/workhub · plugins/agent-ops/skills/handoff-go/SKILL.md · Write a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and…