agentleFS
Sign inStart free
ariaxhanariaxhan/kernel-claude/skills/checkpoint/SKILL.md

checkpoint

Skill15 starsChanged 4 months agoMITView on GitHub

Save bounded progress as kernel.checkpoint/v1 for exact resume after reset. Triggers: checkpoint, save progress, context reset, compact soon, long task.

91 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aside, spinoff and 10 more.

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

    aside

    Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.

    Also in 3 projects that use this

  • AhmedMerzaSkill

    spinoff

    After a branch is finished, harvest the work it made CHEAP — the helper you wrote that four other sites now hand-roll, the plumbing that turned a deferred feature small, the pattern that just split the codebase in two. Produces a follow-up backlog (0–3 candidates, feeding /issue), NEVER commits on the current branch. Invoke with /spinoff at the tail of the chain — after /fix-review has settled the review findings, before the MR merges — or when the user asks \"what else should we do while we're here / what did this unlock / anything to follow up on\". This is ship-check's optional twin — that finds what's MISSING and blocks the merge; this finds what's now CHEAP and blocks nothing. Restraint-gated: \"nothing spun off\" is the common and correct answer, and a finding that would have been equally valid before this branch is not a finding.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 5 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 5 projects that use this

  • seek888Skill

    design-html

    Design finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "implement this design", or after any planning skill. Proactively suggest when user has approved a design or has a plan ready. (gstack) Voice triggers (speech-to-text aliases): "build the design", "code the mockup", "make it real".

    Also in 5 projects that use this

  • +2 more from TheKREATORS
  • +2 more from seek888

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 85 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:

    When to fire (EXP-L21: attention efficiency decays to ~11% late-session.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 85 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
<skill id="checkpoint"><purpose> The small resumable manifest. A handoff transfers a whole session; a checkpoint records bounded progress INSIDE a long-running task so work can continue after a context reset with a fresh, minimal context instead of an inherited transcript.

When to fire (EXP-L21: attention efficiency decays to ~11% late-session; a reset from a checkpoint restores the flat ~50-70k load-bearing line):

  • a long task crosses a natural boundary (a commit lands, a phase completes)
  • context is about to compact, or the session is degrading (anchor-drift, I0.13)
  • the manifest's execution.checkpoints list says so

Checkpoint vs handoff: same task + same session continuation → checkpoint. Ending the session / transferring to a future session with decisions and policy → handoff. </purpose>

<flow> 1. Gather provenance: ```bash git branch --show-current && git rev-parse HEAD && git status --short ```

  1. Write _meta/checkpoints/{task}-{timestamp}.json per schemas/kernel.checkpoint.v1.schema.json:

    • task: goal + handoff_ref/contract_ref if they exist
    • steps_completed: each with EVIDENCE (commit sha, test output, command result), never intent. Receipts describe intent; files describe reality.
    • current_outputs: files produced so far
    • provenance.dirty_tree_sha256: when dirty, sha256 of git diff --binary HEAD
    • pending_steps: what remains, in order
    • resume: position (exact place in the work), entrypoint (skill to re-enter), next_operation (the LITERAL first action — "retarget tests/run-tests.sh lines ~1250 registration tests", not "continue the migration")
    • context (optional): required selectors + budget if the resume should be bounded

    Quote every sha/commit string (all-digit shas parse as integers and fail validation).

  2. Validate — MANDATORY:
    "${CLAUDE_PLUGIN_ROOT:-.}/orchestration/manifest/kernel-manifest" validate _meta/checkpoints/{file}.json
  3. Record:
    agentdb write-end '{"skill":"checkpoint","saved_to":"_meta/checkpoints/{file}.json","position":"..."}'

Resume path: /kernel:ingest discovers the newest manifest automatically (kernel-manifest latest — checkpoints and handoffs share discovery), or accepts an explicit path. </flow>

<hard_stops>

  • steps_completed without evidence → not a checkpoint, a hope. Add evidence or move the step to pending_steps.
  • unvalidated json → does not exist. Validate before reporting done. </hard_stops>
</skill>

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