agentleFS
Sign inStart free
YahyaLendaniYahyaLendani/opus-tuner-claude-skill/skills/wrap/SKILL.md

wrap

Skill14 starsChanged 16 days agoMITView on GitHub

Prepare and verify a handoff for this session, so the user can continue in a fresh one.

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

8 rules. 0 are common, 5 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use at a task boundary, or when the user wants to continue in a fresh session.

    line 8
  2. Distinctive:

    Write the draft. Its facts come from this session's own transcript:

    line 10
  3. Distinctive:

    If it reports that it cannot identify the session, tell the user what it said.

    line 20
  4. Distinctive:

    Do not write the file by hand or point it at another transcript.

    line 21
  5. Distinctive:

    Read the file it names and replace the placeholders.

    line 23
  6. Very specific:

    Write None. when a required section really has nothing to say.

    line 33
  7. Very specific:

    Run the same command again with -Verify added.

    line 35
  8. Very specific:

    Only after verification passes, ask the user to run /clear when they want to continue in a fresh session.

    line 39

“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

Use at a task boundary, or when the user wants to continue in a fresh session.

  1. Write the draft. Its facts come from this session's own transcript:

    # Windows
powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_SKILL_DIR}/../opus-tuner/scripts/brief.ps1" -SessionId "${CLAUDE_SESSION_ID}" -Project "<project directory>"

# macOS / Linux
pwsh -NoProfile -File "${CLAUDE_SKILL_DIR}/../opus-tuner/scripts/brief.ps1" -SessionId "${CLAUDE_SESSION_ID}" -Project "<project directory>"

    If it reports that it cannot identify the session, tell the user what it said. Do not write the file by hand or point it at another transcript.

  2. Read the file it names and replace the placeholders. Keep it under ~600 words; a new session receives it verbatim.

    • Task goal: the outcome the user asked for
    • User constraints: rules the user set that still apply
    • Decisions: what was chosen and why
    • Unresolved problems: what is still broken or undecided
    • Verification results: what was actually run and its result, and what was not verified
    • Next step: one concrete action
    • Dead ends (optional): what was tried and failed

    Write None. when a required section really has nothing to say.

  3. Run the same command again with -Verify added. It checks the required sections, masks credentials and marks the handoff ready. If it reports anything missing, fix that and run it again.
  4. Only after verification passes, ask the user to run /clear when they want to continue in a fresh session. Never try to run it yourself. The session that wrote the handoff is the one that picks it up.

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