agentleFS
Sign inStart free
sschemelsschemel/second-brain-starter/.agents/skills/pause/SKILL.md

pause

Skill0 starsChanged 14 days agoMITView on GitHub

Context stash. Saves a precise checkpoint of the current work state and next steps to 99 - System/memory/Working_Context.md so work can resume in a new session or a different tool. Use when the user types /pause or /stash, says they need to step away, or asks to save or checkpoint context before a reset or handoff.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use resume and init.

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

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • MicrosoftSkill

    init

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Pause / Context Stash

Capture the working state so any agent (Claude Code, Cursor, or other) can resume cold. Extra note from the user: $ARGUMENTS

  1. Capture state: identify the active project, the repo and branch if code is involved (git branch --show-current), the files being edited, what was just done, and what was about to happen next. Include any uncommitted-change caveats.
  2. Write the checkpoint to 99 - System/memory/Working_Context.md. It holds one current checkpoint per active project; history lives in daily notes. Several sessions can run at once (for example one per project), so replace only your own project's section and never overwrite the whole file, or a parallel /pause will clobber another project's checkpoint. If the file has no section for your project, add one at the end after a --- line. A first or only checkpoint uses this shape:
    # Working Context
**Stashed**: YYYY-MM-DD HH:MM (from `date "+%F %H:%M"`) · **Project**: [[10 - Projects/<P>/_Dashboard]]

<2–3 sentences: exact current state, then the explicit next step, specific enough to act on without this chat>

**Open files**: `path`, `path`
**Repo**: `<path>` @ `<branch>` (omit if n/a)
  3. Log it: append a one-line - ⏸️ HH:MM paused: <topic> under ## 💬 Sessions in today's 01 - Daily Chats/YYYY-MM-DD.md (create the note if needed).
  4. Confirm in one line. /sod will surface this checkpoint automatically.

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