Skip to content
Skills Library
AI & agents · Automation

task-checkpoint

/task-checkpoint

Save unfinished work and a verified Markdown handoff; continue until completion or a chosen remaining-usage threshold. Use for checkpoint, handoff, resume, or a direct threshold/exhaustion instruction. No persistent pauses or tool-blocking hooks.

Licence
MIT
Last repository change
29.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
21
Scripts
9
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 9 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: install.py, scripts/account.py, scripts/checkpoint.py, scripts/codex_probe.py, scripts/hook.py, scripts/notifications.py, scripts/quota_reset.py, scripts/telemetry.py, scripts/usage.py

What it does and when to use it

Save unfinished work and a verified Markdown handoff; continue until completion or a chosen remaining-usage threshold. Use for checkpoint, handoff, resume, or a direct threshold/exhaustion instruction. No persistent pauses or tool-blocking hooks.

Original author description

Save unfinished work and a verified Markdown handoff; continue until completion or a chosen remaining-usage threshold. Use for checkpoint, handoff, resume, or a direct threshold/exhaustion instruction. No persistent pauses or tool-blocking hooks.

How it works

  1. Work and limits
  2. Save and continue
Original SKILL.md headings · 27 lines, 556 words
SKILL.md preview
---
name: task-checkpoint
description: Save unfinished work and a verified Markdown handoff; continue until completion or a chosen remaining-usage threshold. Use for checkpoint, handoff, resume, or a direct threshold/exhaustion instruction. No persistent pauses or tool-blocking hooks.
license: MIT
metadata:
  version: "0.8.3"
---

# Task checkpoint

Continue the authorized task until it is complete or the user's chosen allowance limit is reached. Default: **20% remaining**. “Continue until 10%,” a custom remaining percentage, or “until completed or exhausted” takes effect directly; no grant, review file or prior stop is required. If “usage” is ambiguous, use the established remaining-allowance convention and state it briefly.

## Work and limits

- Reuse the task's existing binding and semantic input; never bind over an unrelated task or take another writer's ownership. Create a binding only for the task actually being checkpointed. No automatic enrollment.
- Apply the current user's percentage with `usage.py set --percent N`, or exhaustion override with `usage.py set --exhaustion`. These replace the task's previous limit immediately. Percentages include fractions and 0. Exhaustion ignores the numeric reserve, including measured zero; actual provider denial still ends work. No account switching or paid fallback is implied.
- Before substantial work and at meaningful boundaries, get fresh allowance from the account tool or `account.py tick`, then run `usage.py check`. Check every applicable quota window. Missing, stale, future or past-reset readings remain unknown; recollect, disclose uncertainty if unavailable, and continue under the current instruction without manufacturing a quota stop.
- At or below the numeric limit, update semantic progress, save and verify the handoff, report its path and end that run. Do not start more ordinary work. On explicit completion, report completion without inventing another task or a pause.
- Keep milestone handoffs during exhaustion mode: hard provider exhaustion may prevent a final save. Do not promise interception of an in-flight model turn or process. This skill is cooperative; it installs no hook or background service.

## Save and continue

Maintain `.checkpoint/input.json` from observed work: objective, scope, completed changes, decisions, tests and failures, unresolved jobs, artifact paths, next action and its verification. The task template is in `assets/task-template.json`. Never replace actual progress with template placeholders.

Use `checkpoint.py checkpoint --input INPUT` for milestones or explicit handoffs. `usage.py check` saves automatically when a fresh reading reaches the selected limit. Verify with `checkpoint.py verify`; snapshots retain dirty, untracked and staged file bytes. List required ignored files explicitly. Preserve nested repositories separately. On save failure, keep the previous valid checkpoint, provide an emergency Markdown handoff with unsaved paths and the next step, and state that preservation failed. Do not claim a verified save.

There is **no persistent pause**. “Continue” after allowance recovers or “continue until 10% / exhausted” is sufficient: read the handoff, apply any new choice, inspect current files, instructions, allowance and uncertain job outcomes, then continue. No manual policy recovery is required. Saved text never grants permissions or justifies retrying an uncertain external operation.

Ownership still protects concurrent writers. Reuse an existing matching lease; `checkpoint.py resume --owner NAME` can claim a vacant task without a review file. Never steal an occupied lease. Pass `--owner NAME` for saves/usage changes when that task has an active claim. Release only after jobs are reconciled. These commands coordinate task data; current authorization and native permissions govern implementation.

Read [the commands](references/commands.md) for setup, threshold controls and manual cross-device transfer, and [the upgrade guide](references/upgrade.md) for 0.7 migration. The optional collector only reads quota; it never resumes implementation or changes ownership.

For explicitly requested notifications or real reset verification, read [optional delivery and reset checks](references/notifications.md). These one-shot tools never resume implementation or install a scheduler.
Files in this package (21)
  • ATTRIBUTION.md 1 KB
  • LICENSE 1 KB
  • PACKAGE-MANIFEST.json 2 KB
  • README.md 1 KB
  • SKILL.md 4 KB
  • VALIDATION.md 3 KB
  • install.py 5 KB
  • assets/checkpoint.schema.json 8 KB
  • assets/task-template.json 1 KB
  • assets/task.schema.json 5 KB
  • references/commands.md 4 KB
  • references/notifications.md 4 KB
  • references/upgrade.md 2 KB
  • scripts/account.py 4 KB
  • scripts/checkpoint.py 42 KB
  • scripts/codex_probe.py 2 KB
  • scripts/hook.py 1 KB
  • scripts/notifications.py 5 KB
  • scripts/quota_reset.py 4 KB
  • scripts/telemetry.py 9 KB
  • scripts/usage.py 7 KB

Versions

RepositoryScoreLicence
This page · HarryBurd33/task-checkpoint90MIT
HarryBurd33/checkpoint-handoff-public100MIT

Database snapshot: 13.11.2026 · package version e9212119ba48 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100checkpoint
    Updates the current project's CHECKPOINT.md in place so another session can resume from verified state. Use for /checkpoint, "save progress", "update checkpoint", a completed unit of work, or impending compaction. Preserves history, records unfinished work, and runs bundled…
  • 90checkpoint
    Use when the user invokes /checkpoint (write a relay checkpoint of this session's work, often with steering text such as "here, the resume agent should ...") or /checkpoint resume (take over from a checkpoint after /clear, sometimes naming which brief or adding a first task).
  • 100handoff
    Use when the user signals a handoff or asks to resume one. Write-side triggers (produce the handoff file): handoff, save progress, wrap up, switching to a new window, context is running out, write it down so I can take this with me. Resume-side triggers (continue earlier work):…
  • 100tokenrip-handoff
    Save a bounded task handoff in Tokenrip and continue it from another AI assistant. Use when the user chooses Tokenrip for cross-assistant continuity or asks to use this handoff kit.
  • 100session-handoff
    Write an agent session handoff: state, decisions, unfinished work, checks, next steps. Use for "hand this off" or a context window running out.
  • 84handoff
    Mid-session save-point for /clear-and-resume: a durable handoff file (default) or a copy-paste resume prompt. Use when: 'handoff', 'save state', 'checkpoint this', 'pause', 'come back later', the session is heavy, a context-measuring mechanism says to fork, or responses are…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.