How do I install the Save Progress skill?

Run npx skillmds@latest add jgjake2/save-progress in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Save Progress safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Save Progress?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Save Progress free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Save Progress?

jgjake2 (@jgjake2) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Save Progress by jgjake2 — Agent Skill

Name: Save Progress
Author: jgjake2

Save Progress

Save a checkpoint of the current task -- what has been done plus a concrete resume plan -- to the project's progress directory. Use when check-usage returns band "stop", and at intermediate checkpoints during any long task.

jgjake2 6dc2d11 2 files · 9.8 KB Updated Sep 17, 2026

File contents

save-progress

Writes a timestamped JSON checkpoint (plus a readable .md copy) to progress/, and updates progress/latest.json so resuming never requires a hand-copied filename.

How to call it

The two fields are long multi-line prose, so they go through a JSON file rather than command-line arguments (which would be a quoting minefield on Windows).

Step 1 -- write the payload to progress-payload.json:

{
    "task": "One-line description of what the overall task is",
    "progress": "Everything accomplished so far: files changed, decisions made, intermediate results, anything already verified.",
    "resumePlan": "The concrete next steps, remaining work, and any dependencies or prerequisites.",
    "notes": "Optional. Anything else the next session needs."
}

Step 2 -- run:

node .claude/skills/save-progress/save-progress.js --payload progress-payload.json --consume

--consume deletes the payload file after a successful save.

progress and resumePlan are required and must be non-empty.

To pipe the JSON on standard input instead, pass --stdin explicitly:

... | node .claude/skills/save-progress/save-progress.js --stdin

--stdin is opt-in on purpose: without it, a harness that leaves stdin open would block this script forever, and it runs precisely when the budget is nearly gone.

Response

{ "saved": true, "path": "...", "markdownPath": "...", "latestPointer": "...", "savedAt": "..." }

On failure: { "saved": false, "error": "..." } with a non-zero exit code. A failed save leaves no partial checkpoint behind.

Writing a good checkpoint

The resume plan is read by a session with no memory of this one. Name files by full path, state decisions rather than implying them, and make the first next-step something concrete enough to start on immediately. Assume nothing carries over.

Tell the user the checkpoint path after saving.

---name: save-progressdescription: Save a checkpoint of the current task -- what has been done plus a concrete resume plan -- to the project's progress directory. Use when check-usage returns band "stop", and at intermediate checkpoints during any long task.---# save-progressWrites a timestamped JSON checkpoint (plus a readable `.md` copy) to `progress/`, andupdates `progress/latest.json` so resuming never requires a hand-copied filename.## How to call itThe two fields are long multi-line prose, so they go through a JSON file rather thancommand-line arguments (which would be a quoting minefield on Windows).**Step 1** -- write the payload to `progress-payload.json`:```json{ "task": "One-line description of what the overall task is", "progress": "Everything accomplished so far: files changed, decisions made, intermediate results, anything already verified.", "resumePlan": "The concrete next steps, remaining work, and any dependencies or prerequisites.", "notes": "Optional. Anything else the next session needs."}```**Step 2** -- run:```node .claude/skills/save-progress/save-progress.js --payload progress-payload.json --consume````--consume` deletes the payload file after a successful save.`progress` and `resumePlan` are required and must be non-empty.To pipe the JSON on standard input instead, pass `--stdin` explicitly:```... | node .claude/skills/save-progress/save-progress.js --stdin````--stdin` is opt-in on purpose: without it, a harness that leaves stdin open would blockthis script forever, and it runs precisely when the budget is nearly gone.## Response```json{ "saved": true, "path": "...", "markdownPath": "...", "latestPointer": "...", "savedAt": "..." }```On failure: `{ "saved": false, "error": "..." }` with a non-zero exit code. A failed saveleaves no partial checkpoint behind.## Writing a good checkpointThe resume plan is read by a session with **no memory of this one**. Name files by fullpath, state decisions rather than implying them, and make the first next-step somethingconcrete enough to start on immediately. Assume nothing carries over.Tell the user the checkpoint path after saving.

Frequently asked questions