cleanup SKILL.md skillA
cleanup from higoralves/orc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add higoralves/orc/cleanup@git:20261020.7a1f356Pins git:20261020.7a1f356 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- higoralves/orc
- Path
orc/skills/cleanup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.7a1f356, committed Oct 20, 2026
- Size
- 5,014 bytes
- Repository stars
- 7
- License
- MIT
Clean up after completed or abandoned orc sessions — removes workspace state, registry entry, git worktree, and optionally the merged branch. Destructive; always previews and asks first. Workspace-aware.
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
# /orc:cleanup Close the loop on finished orc work: remove the workspace state, the worktree and, when safe, the local feature branch. ## Arguments - `--auto[=guided|full]` — autopilot level for this run; overrides `interaction_policy`. Ladder and hard-outward exemption: `orc:gates` §6. - `<session-id-or-branch>` — optional. Clean exactly one session, by `sessionId` (`orc-state sessions`, schema `orc:state-protocol`) or branch name, sanitized or raw. - `--all-completed` — clean every session whose `status` is `completed` or `abandoned`. Every safety check still applies per session. - `--dry-run` — print what would happen; change nothing. Recommended for the first run. - `--per-repo` — workspace mode: clean each linked repo as its PR merges. Use only when abandoning some repos (rare). - `--down-volumes` — also remove a torn-down environment's named volumes. Default keeps them: the next boot reuses DB data. NOTE: at `guided` or `full`, the standard plan (state dir, clean worktree, merged branch) auto-applies after printing. Anomalies still gate at every level: partial workspace merges, unmerged branches, a dirty worktree. ## Preconditions > **🛑 Destructive run** > …
Read the whole file at its exact version.
How to install
mdr add higoralves/orc/cleanup@sha256:aaebb9c746ee9302The line at the top of this page pins the label git:20261020.7a1f356, 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_3gfslr2nmqc6342x)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 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 (5014 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
higoralves/orc · 7 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3gfslr2nmqc6342x GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/cleanup GET https://markdownregistry.com/api/v1/blob/aaebb9c746ee93020e7becc5fe1ed5f727b0f910fd99e8b686e5fc941383c479
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.