agentleFS
Sign inStart free
kuldeep-jadejakuldeep-jadeja/claude-handoff-plugin/skills/resume/SKILL.md

resume

Skill1 starsChanged 12 days agoMITView on GitHub

Reload the latest session handoff (knowledge/handoffs/CURRENT.md), or an archived one, and get ready to continue the work it describes. Use when the user says "resume", "where did we leave off", "continue from last time" or "load the handoff".

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pause, status 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.
  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 15 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    No argument: read knowledge/handoffs/CURRENT.md and knowledge/handoffs/AUTO.md (whichever exist), however old they are.

    line 12
  2. Very specific:

    Check the context: run git branch --show-current and compare it with the Branch: in the handoff header.

    line 15
  3. Distinctive:

    Do not start the work, edit files or run anything else until the user confirms.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 53 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

Reload a saved handoff and get ready to continue the work it describes.

Argument (whatever the user typed after the command, may be empty): $ARGUMENTS

  1. Find the handoff:
    • No argument: read knowledge/handoffs/CURRENT.md and knowledge/handoffs/AUTO.md (whichever exist), however old they are.
    • With an argument: look in knowledge/handoffs/archive/ for a file whose name or # Handoff: title contains the argument (ignore case). If several match, list them and ask which one. If none match, say so and show the five newest archive files.
    • Nothing found at all: say there is no saved handoff in this project and that the user can save one by asking for a handoff (the handoff skill). Stop there.
  2. Check the context: run git branch --show-current and compare it with the Branch: in the handoff header. Note how old the handoff is from its Updated: line.
  3. Reply in at most five short lines:
    • what was in progress (the handoff's topic and goal),
    • the very next step from "Next steps",
    • any open question or blocker it lists,
    • a warning if it was written on another branch, or is more than 14 days old,
    • then ask: "Continue from here?"
  4. Do not start the work, edit files or run anything else until the user confirms.

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