agentleFS
wrg32786wrg32786/aigent-os/skills/pause/SKILL.md

pause

Skill25 starsChanged 7 days agoMITView on GitHub

Pause current work with resumable state. Use when pausing a task or stopping work temporarily before returning to it.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use 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.
  • MicrosoftSkill

    init

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 0

    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:

    Create a Capsule v2 with status: paused capturing full execution state for later resume.

    line 8

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

/pause — Pause current work with resumable state

Create a Capsule v2 with status: paused capturing full execution state for later resume.

Trigger

/pause or /pause waiting on {blocker}

Flow

  1. Capture state — gather from current session:
    • Objective (what we were working on)
    • Files touched (from tool call history)
    • Skills and agents used
    • Last verified state (what was confirmed working)
    • Open questions and blockers
  2. Determine waiting_on — from argument or ask:
    • will — needs the operator's decision or input
    • agent — waiting on a sub-agent to complete
    • tool — waiting on external tool/API/deploy
    • external — waiting on someone outside the system (a colleague, a client, etc.)
  3. Set resume_trigger:
    • will → manual (the operator decides when to resume)
    • agent → open (resumes at next session boot, which checks agent status)
    • tool → manual (check tool status on resume)
    • external → open (resumes at next session boot, surfacing the wait)
  4. Write capsule — use /context-capsule schema with status: paused
  5. Update BODY_STATE.json — set state.last_capsule with paused capsule info
  6. Output:
    Paused: {objective}
    Waiting on: {waiting_on}
    Resume trigger: {resume_trigger}
    Next action: {next_valid_action}
    Resume with /resume (offered automatically at next session boot).

Related

  • /resume — pick up paused work
  • /context-capsule — the underlying capsule system
  • [[concepts/Capsule v2 Doctrine]] — design rationale

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.