agentleFS
Sign inStart free
ucsandmanucsandman/claude-skills/wrap/SKILL.md

wrap

Skill5 starsChanged 2 months agoMITView on GitHub

Write session handoff notes and a resume prompt when wrapping up.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use start, update and 9 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.
  • AnthropicSkill

    start

    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

  • AnthropicSkill

    update

    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

  • LangChainSkill

    remember

    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

  • termdockSkill

    recall

    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 AzureSkill

    build

    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

  • SentrySkill

    review

    Fixture review skill.

    Also in 7 projects that use this

  • +1 more from anthropics

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Persist: Run /handoff-save. If the bundle CLI is unavailable, write the bullets to the project's progress-notes doc instead.

    line 20
  2. Distinctive:

    Hand control back: Never suggest stopping for the day or postponing — pacing is the user's call.

    line 22

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wrap

End a session so the next one starts at full speed: stop at a seam, lock state, persist it, emit a resume prompt.

Steps

  1. Stop at the seam. Finish only the smallest in-flight unit (the current edit plus its verification). Start nothing new.
  2. Lock state in bullets:
    • Goal (one line) and current phase
    • Done and verified — with the evidence (command + result)
    • In progress — exact file and step
    • Next concrete action
    • Deviations from plan made this session and why (from the DEVIATIONS log, if kept)
    • Risks/gotchas that will bite a fresh session
  3. Persist. Run /handoff-save. If the bundle CLI is unavailable, write the bullets to the project's progress-notes doc instead.
  4. Resume prompt. Emit one contiguous pasteable block containing: project directory, recommended model and effort level, /handoff-load <bundle-name>, and the next concrete action. No commentary inside the block.
  5. Hand control back. Never suggest stopping for the day or postponing — pacing is the user's call.

Common mistakes

  • Vague notes ("continue the refactor") — the next session needs file paths and the exact next command.
  • Resume prompt missing model/effort/directory — sessions run across many projects; make it self-locating.
  • Doing "one more improvement" after wrap is requested.
  • Locking state that was never verified — "done" without evidence becomes a false fact in the next session.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free