agentleFS
Sign inStart free
adventurewave-labsadventurewave-labs/apsl-core/skills/stop/SKILL.md

stop

Skill0 starsChanged 4 months agoMITView on GitHub

Request a pause for explicit human approval before proceeding. Use as a checkpoint before irreversible operations like deploy, delete, publish, or any action with production impact.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use status.

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

    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 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat any non-approval response as a modification request.

    line 48

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

stop — Checkpoint Skill

Execution Steps

  1. Summarize what has been accomplished so far in the current workflow.
  2. State clearly what action comes NEXT if execution continues.
  3. State the reason for this checkpoint (if provided).
  4. Show the checkpoint block:
══════════════════════════════════════════
⏸  CHECKPOINT
══════════════════════════════════════════
Completed:
  ✓ [list what's done]

Next action if you approve:
  → [exact next step, be specific]

Reason for checkpoint:
  [reason, or "manual checkpoint in workflow"]

To review before approving:
  - [specific files, diffs, or outputs to check]
══════════════════════════════════════════
Reply "approved", "go", or "proceed" to continue.
Reply anything else to modify the plan.
══════════════════════════════════════════
  1. Request that execution not proceed until the user explicitly approves.
  2. Treat any non-approval response as a modification request.

IMPORTANT: This skill places a checkpoint INSTRUCTION in the prompt. It does not technically enforce a halt. For guaranteed gating of irreversible actions, configure the agent runtime's tool-permission system to require approval for the relevant tools.

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