wrap
Skill1 starsChanged 38 days agoMITView on GitHub
Use when the user types /wrap or asks to wrap up, save progress, or checkpoint the session before stopping, rebooting, or switching tasks.
- Reads credentials
46 other projects use a version of this.
Adopted by
Most recently taken up by
- odakin/claude-configtheir own version, first seen Nov 15, 2026
- fjwood69/moritheir own version, first seen Nov 10, 2026
- rhasselle-oddball/claude-skillstheir own version, first seen Nov 8, 2026
- jolleyDesign/claude-skillstheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- mag123c/toktracktheir own version, first seen Nov 3, 2026
Used with
Projects with it also use start, update and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 5 projects that use this
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
LangChainSkillremember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.
Also in 3 projects that use this
termdockSkillrecall
Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.
Also in 3 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 7 projects that use this
- +1 more from anthropics
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- UniClipboard/UniClipboard★ 2ksame name
- team-attention/stanford-cs146s-kr★ 294same name
- egregore-labs/egregore★ 293same name
- mag123c/toktrack★ 196same name
- neurofoo/agent-skills★ 111same name
- lsnackerman/raw-clauding-skills★ 45same name
- fjwood69/mori★ 32same name
- YahyaLendani/opus-tuner-claude-skill★ 14same name
- jackjin1997/ClawForge★ 12same name
- ucsandman/claude-skills★ 5same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- skills/fable-setup/templates/CLAUDE.mdCLAUDE.md
- delegateSkill
- fable-setupSkill
- product-videoSkill
- tokenwatchSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Use the memory directory and format from the system prompt.
- Distinctive: line 25
Update the existing file for a project or topic.
- Very specific: line 28
Keep the MEMORY.md index in sync: one line per file, no duplicates.
- Very specific: line 38
If a project had multi-step work but no resume doc, create TASKS.md at its root.
- Very specific: line 42
If the workspace has logs/journal.md, append one dated entry (## YYYY-MM-DD: <topic>): 3–6 bullets covering decisions, progress, blockers, …
- Very specific: line 49
Never stage secrets: .env, keys, tokens, credential or config files with passwords.
- Distinctive: line 50
Commit on the current branch with a clear message and the session's attribution lines.
- Distinctive: line 51
Never push: Never force, amend, or rebase.
- Distinctive: line 58
Stop background tasks that shouldn't outlive the session (servers, watchers), unless the user wants them running.
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wrap
Checkpoint the session so a fresh session can resume with no scrollback. Capture state in the places that already exist, commit local repo work, and report.
Work through every step. A step with nothing to do gets one line in the report ("Journal: n/a, no journal in this workspace").
1. Inventory (no writes yet)
Note, from this conversation:
- Projects touched: each directory where files were created or edited.
- Decisions: what was chosen, and why it matters later.
- State: what's done, what's in progress, what's blocked (and on what).
- Next step: the single concrete action to resume with.
- Loose ends: background tasks/servers/downloads still running; actions waiting on the user (reboot, login, approval).
2. Memory
Use the memory directory and format from the system prompt.
- Update the existing file for a project or topic. Create a new one only for a genuinely new fact, preference, or project.
- Save user preferences and corrections as
feedbackmemories, with Why and How to apply. - Store absolute dates, never "today" or "tomorrow".
- Keep the
MEMORY.mdindex in sync: one line per file, no duplicates. - Skip anything the repo, docs, or git history already record.
3. Project resume docs
For each project touched, update the resume docs it already has: NEXT.md, TASKS.md, CONTEXT.md, plan files with checkboxes, and status sections in a project CLAUDE.md.
- Tick finished items and add newly found ones.
- Move the ← START HERE marker (or equivalent) to the next step.
- Record blockers and exactly how to clear them.
If a project had multi-step work but no resume doc, create TASKS.md at its root. Otherwise create nothing new.
4. Journal
If the workspace has logs/journal.md, append one dated entry (## YYYY-MM-DD: <topic>): 3–6 bullets covering decisions, progress, blockers, and the resume pointer.
5. Git (every repo touched)
For each touched directory inside a git repo:
git status. Read.gitignoreif unsure what belongs.- Stage only files from this session's work, by explicit path. Never
git add -A/.. - Never stage secrets:
.env, keys, tokens, credential or config files with passwords. If one shows as modified, leave it out and flag it in the report. - Commit on the current branch with a clear message and the session's attribution lines.
- Never push. Never force, amend, or rebase.
- Report unrelated uncommitted changes you left alone.
A repo that is public (per memory or CLAUDE.md) gets an extra secrets check of the staged diff before committing.
6. Loose ends
Stop background tasks that shouldn't outlive the session (servers, watchers), unless the user wants them running. Leave user-started processes alone. List everything still running or pending.
7. Report (this exact shape)
**Wrapped.**
- Memory: <files created/updated, or n/a>
- Docs: <files updated, or n/a>
- Journal: <entry added, or n/a>
- Git: <repo: commit hash + message | nothing to commit | not a repo>
- Still running / needs you: <items, or none>
**To resume:** say "<short phrase>". Starts at <file / next step>.Common Mistakes
| Mistake | Fix |
| Creating a new notes file when a NEXT.md/TASKS.md exists | Update the existing doc |
git add . sweeps in unrelated or secret files | Stage explicit paths from this session only |
| Pushing "since it's committed anyway" | Never push; the user pushes |
| Memory duplicates an existing file | Search the memory dir first; update in place |
| Relative dates ("tomorrow") in memory/docs | Convert to YYYY-MM-DD |
| Skipping a step silently | Every step appears in the report, even as n/a |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

