stale-data-cleanup SKILL.md skillA

stale-data-cleanup from codealive-ai/pragmatic-orchestration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add codealive-ai/pragmatic-orchestration/stale-data-cleanup@git:20261115.d42a0c6

Pins git:20261115.d42a0c6 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
codealive-ai/pragmatic-orchestration
Path
skills/stale-data-cleanup/SKILL.md
Versions recorded
3
Latest version
git:20261115.d42a0c6, committed Nov 15, 2026
First version recorded
Nov 15, 2026
Size
14,955 bytes
Repository stars
73
License
MIT

Find and remove stale data on a developer's machines by evidence, with verdicts instead of a checklist for the owner: finished agent workspaces and git worktrees, old task checkouts, build and run output, package and model caches, container images, on a laptop and on remote dev hosts. Use when a disk is full or keeps filling, or the user asks to free space, clean up after coding agents, close old workspaces or worktrees, audit what takes the space, or work out what is obsolete…

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

# Stale Data Cleanup

A full disk on a machine where many agents work is rarely old junk. It is
finished work nobody closed, caches, and a remainder only the owner can judge.
The job is to tell the three apart **by evidence**, remove the first two without
troubling the owner, and bring them a short list for the third.

The owner asked because they are at a loss. A list of two hundred checkboxes
hands the problem back. **They want verdicts.** Every candidate ends in one of
three states: REMOVED, KEPT with a one-line reason, or ASKED, and ASKED is rare.

## The role

- **Run this in Coordinator Mode.** Load `coordinator-mode` and enter it as that
  skill describes (executors, journal, capsule); it loads
  `pragmatic-orchestration` for the mechanics. Invoking this skill **is** the
  explicit request that mode asks for: tell the user in one line that this runs
  as a multi-agent job, and keep the mode on until they end it. After a
  compaction reread this file and the journal first.
- **You are the strongest model available.** Wrong verdict rules destroy data,
  so rules, acceptance and decisions stay with you.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gono3x2fciy2bauz/5b5204a2d34fd6e4bbef802b0d3cd3b4df6f41fe779f09f4299fb2ce4ce75f6f.json

Then /plugin install stale-data-cleanup@markdownregistry-gono3x2fciy2bauz in Claude Code. It installs git:20261115.d42a0c6, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add codealive-ai/pragmatic-orchestration/stale-data-cleanup@sha256:5b5204a2d34fd6e4

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

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in codealive-ai/pragmatic-orchestration/stale-data-cleanup since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of stale-data-cleanup from somewhere else? Ask it: where did my stale-data-cleanup come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, all committed on Nov 15, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261115.d42a0c6 latest2026-11-15 d42a0c6 14,955 BA view · diff
git:20261115.a557a392026-11-15 a557a39 12,587 BA view · diff
git:20261115.aa7f8572026-11-15 aa7f857 14,633 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

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 (14955 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

codealive-ai/pragmatic-orchestration · 73 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_gono3x2fciy2bauz
GET https://markdownregistry.com/api/v1/resolve?ref=codealive-ai/pragmatic-orchestration/stale-data-cleanup
GET https://markdownregistry.com/api/v1/blob/5b5204a2d34fd6e4bbef802b0d3cd3b4df6f41fe779f09f4299fb2ce4ce75f6f

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 codealive-ai/pragmatic-orchestration

pragmatic-orchestration Plugin marketplace
codealive-ai/pragmatic-orchestration · .claude-plugin/marketplace.json · Pragmatic multi-agent orchestration: independent review and steerable delegation across Codex, Claude Code, OpenCode…
v5.18.2 · audit A · 73 stars
AGENTS.md AGENTS.md file
codealive-ai/pragmatic-orchestration · AGENTS.md
git:20261115.d42a0c6 · audit A · 73 stars
CLAUDE.md CLAUDE.md file
codealive-ai/pragmatic-orchestration · CLAUDE.md
git:20260917.07137c0 · audit B · 73 stars
coordinator-mode SKILL.md skill
codealive-ai/pragmatic-orchestration · skills/coordinator-mode/SKILL.md · Switch this session into Coordinator Mode: a long-lived role that plans, designs verification, delegates implementation…
git:20261117.06e3c1f · audit A · 73 stars
pragmatic-orchestration SKILL.md skill
codealive-ai/pragmatic-orchestration · skills/pragmatic-orchestration/SKILL.md · Orchestrate coding agents economically: reach an accepted result cheaper and faster by delegating implementation…
git:20261119.7332f26 · audit A · 73 stars
remote-agents SKILL.md skill
codealive-ai/pragmatic-orchestration · skills/remote-agents/SKILL.md · Operate dedicated remote Linux/Windows hosts that run coding agents. Use for provisioning and hardening an agent VM…
git:20261029.b6b1bab · audit A · 73 stars

Every file in codealive-ai/pragmatic-orchestration

Browse by kind, by grade A, or by owner.