todoArchive SKILL.md skillA
todoArchive from blackorange0506/prompt-todo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add blackorange0506/prompt-todo/todoArchive@git:20260914.d1a088ePins git:20260914.d1a088e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- blackorange0506/prompt-todo
- Path
template/.claude/skills/todoArchive/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260914.d1a088e, committed Sep 14, 2026
- First version recorded
- Sep 6, 2026
- Size
- 3,086 bytes
- Repository stars
- 4
- License
- MIT
Move every done ([x]) item out of the user's todo file (TODO.<git user.name>.md, resolved as in the todo rules) into TODO.<git user.name>.archive.md, verbatim, and report what moved. Done items are never deleted — the archive keeps the ids so the next id stays unique, and git picks the move up in the user's normal commits (no git checks, no commits by this skill). Use when the user wants to clean the done prompts out of the todo file — phrases like '/todoArchive', 'archive the done items'…
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
# /todoArchive Clears finished prompts out of the user's todo file without losing them: they move to the archive file. "Remove" never means delete — the **Ids** rule in the todo rules (`.claude/prompt-todo/RULES.md`) derives the next id from the highest id across the todo file *and* its archive, so an archived item still pins its number. The archive is the history; git records the move whenever the user next commits, so this skill neither checks git state nor commits anything. ## What Claude does 1. **Resolve and read the user's todo file** — `TODO.<name>.md` at the repo root, `<name>` from `git config user.name` (the rule in the todo rules). Never another user's file. Run the Autoincrement rule first, as on any touch. Edit tool only. 2. **Collect the candidates**: every top-level `- [x]` / `- [X]` item together with the indented sub-bullets that belong to it. Rows carrying one of the ignore tags of the rules (`QA:` / `Admin:` by default) are candidates too once the user has ticked them: moving a row verbatim is not working, rewriting or ticking it, so the ignore rule is not broken. …
Read the whole file at its exact version.
How to install
mdr add blackorange0506/prompt-todo/todoArchive@sha256:6be6afec4cda41fcThe line at the top of this page pins the label git:20260914.d1a088e, 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_umm2a3zsxmnrnbbu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 6, 2026 and Sep 14, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.d1a088e latest | 2026-09-14 | d1a088e | 3,086 B | A | view · diff |
| git:20260906.6689d67 | 2026-09-06 | 6689d67 | 2,884 B | A | view · diff |
| git:20260906.c1d57b6 | 2026-09-06 | c1d57b6 | 2,911 B | A | view |
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 (3086 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
blackorange0506/prompt-todo · 4 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_umm2a3zsxmnrnbbu GET https://markdownregistry.com/api/v1/resolve?ref=blackorange0506/prompt-todo/todoArchive GET https://markdownregistry.com/api/v1/blob/6be6afec4cda41fc1f32a89f96bbfc8716b605031a76cefedc029a354e0cac21
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.