fleet-sweep SKILL.md skillA

fleet-sweep from petekp/coordinator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add petekp/coordinator/fleet-sweep@git:20261115.aace188

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

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
petekp/coordinator
Path
skills/fleet-sweep/SKILL.md
Versions recorded
5
Latest version
git:20261115.7064718, committed Nov 15, 2026
First version recorded
Nov 14, 2026
Size
6,829 bytes
Repository stars
46
License
MIT

Clean up after a coordinator's fleet. Finds and removes finished delegates' tabs, worktrees, branches and processes, and asks the user about the rest. Use at a coordinator's start, after compaction or a restart, when a delegate settles or a PR merges, and before each status reply.

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

# Fleet sweep

Clean up without being asked. The sweep script decides what is safe to
delete. Act on its verdicts in the turn you see them, and ask the user only
about what would lose work.

`<scripts>` below is this skill's `scripts/` folder.

## When

Sweep at Start, after compaction or a restart, whenever the fleet watcher
fires, and before every status reply. The sweep before each reply catches a
merged PR the watcher was not given. Clean up a delegate in the same turn
its task finishes, so no finished delegate waits for a later sweep.

## Run the report

```bash
<scripts>/sweep.py report <repo>... [--base <branch>]... [--keep <path>]...
```

Pass the domain's main checkouts, any base branches beyond the remote's
default, and the checkouts that must stay, such as a long-lived release
worktree. The backlog's Boundary section holds this line; add it when
missing. The report takes about half a minute and changes nothing. Each row
starts with a verdict:

| Verdict | Meaning | Do |
|---|---|---|
| SAFE | Finished, and nothing would be lost | Remove it this turn, without asking |
| CLOSE | Finished, but a session still runs there | Close it when it is your delegate, then remove |
…

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_rgn6hzrnxnocpgtc/6ba5de876c6e93d5c5d9ad840588df27da1ea87ac23ffc95cca5e03c2288dcae.json

Then /plugin install fleet-sweep@markdownregistry-rgn6hzrnxnocpgtc in Claude Code. It installs git:20261115.7064718, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add petekp/coordinator/fleet-sweep@sha256:71a680b5490d6863

The line at the top of this page pins the label git:20261115.aace188, 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_rgn6hzrnxnocpgtc.svg)](https://markdownregistry.com/a/art_rgn6hzrnxnocpgtc)

2 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 petekp/coordinator/fleet-sweep 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 fleet-sweep from somewhere else? Ask it: where did my fleet-sweep 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 5 versions of this file, between Nov 14, 2026 and Nov 15, 2026, more than one a day.

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

versioncommittedcommitsizeaudit
git:20261115.7064718 latest2026-11-15 7064718 6,829 BA view · diff
git:20261115.a9c30ef2026-11-15 a9c30ef 6,850 BA view · diff
git:20261115.aace1882026-11-15 aace188 6,830 BA view · diff
git:20261115.bc45d342026-11-15 bc45d34 6,063 BA view · diff
git:20261114.4f793fe2026-11-14 4f793fe 6,061 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 (6829 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

petekp/coordinator · 46 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rgn6hzrnxnocpgtc
GET https://markdownregistry.com/api/v1/resolve?ref=petekp/coordinator/fleet-sweep
GET https://markdownregistry.com/api/v1/blob/71a680b5490d6863a22451d1bbdb4a447318d73ab974bae8713dbc908e57caa6

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 petekp/coordinator

coordinator SKILL.md skill
petekp/coordinator · skills/coordinator/SKILL.md · Run this session as the coordinator for one domain, such as a project, a product area or a set of tools. The user…
git:20261115.aace188 · audit A · 46 stars

Every file in petekp/coordinator

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