Agent skill

Checkpoint

Save a compact continuation checkpoint so current work survives context compaction or a later session.

Install Checkpoint

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/checkpoint .claude/skills/checkpoint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .claude/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/checkpoint

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/checkpoint .agents/skills/checkpoint && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .agents/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/checkpoint .cursor/skills/checkpoint && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .cursor/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/checkpoint

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/checkpoint .gemini/skills/checkpoint && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .gemini/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/checkpoint .github/skills/checkpoint && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .github/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill checkpoint -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research checkpoint --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/checkpoint .opencode/skills/checkpoint && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "checkpoint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/checkpoint into .opencode/skills/checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checkpoint", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: checkpoint
GitHub stars: 145
Token cost: ~999 tokens
SKILL.md length: 388 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Save a compact continuation checkpoint so current work survives context compaction or a later session.

Works in 3 steps: Gather State → Write Checkpoint → Confirm
The active context is becoming long
SKILL.md covers When to Use, When This Skill Is Invoked, Schema Rules and Multiple Checkpoints, plus 1 more section
Calls git

What it does

Checkpoint is an agent skill from flonat/flonat-research. Save a compact continuation checkpoint so current work survives context compaction or a later session. Use when the active context is becoming long or work must pause without changing client or machine ownership. For an explicit cross-session/client transfer, use $handoff.

Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff and Context engineering. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

The active context is becoming long
Work must pause without changing client
Machine ownership

Example prompts

“/checkpoint”

Requirements

Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(git*), Bash(date*), Bash(wc*), Glob

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Gather State
Write Checkpoint
Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Bash(git*)
- Bash(date*)
- Bash(wc*)
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Checkpoint loads about 999 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~71
When it runs · the whole SKILL.md, loaded when a task matches: ~999

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 388 words, ~999 tokens.

Download SKILL.mdSave it as .claude/skills/checkpoint/SKILL.md (or your agent's skills folder).

name: checkpoint
description: Save a compact continuation checkpoint so current work survives context compaction or a later session. Use when the active context is becoming long or work must pause without changing client or machine ownership. For an explicit cross-session/client transfer, use $handoff.
allowed-tools: Read, Write, Edit, Bash(git*), Bash(date*), Bash(wc*), Glob

Checkpoint — Save Session State

Snapshot the current session's progress to a YAML file so it can be restored after context compaction or in a new session. This is NOT a session log (narrative) or context save (profile/focus) — it's a machine-readable state dump for continuity.

When to Use

Before a session is likely to hit context compression (many tool calls, long outputs)
At phase boundaries in multi-phase work
When the user says "save state", "checkpoint", "save progress"
Proactively when you sense context is getting large — don't wait to be asked

When This Skill Is Invoked

Step 1: Gather State

Collect the following from the current conversation context:

Project — which project directory are we working in?
Task — what was the user's original request this session?
Files modified — list every file you've created or edited this session (use git diff --name-only if in a git repo, plus any new untracked files)
Decisions made — key choices and their rationale (e.g., "chose LaTeX over Markdown because...", "used sonnet for cron jobs to reduce cost")
Current step — where in the plan are we? What just completed? What's next?
Blocked items — anything that couldn't be completed and why
Open questions — unresolved ambiguities that need user input

Step 2: Write Checkpoint

Write to .planning/checkpoint.yaml in the active project directory. If no project directory is obvious, write to the Task Management root.

yaml

# Auto-generated by checkpoint — do not edit manually
created: "YYYY-MM-DDTHH:MM:SS"
session_id: "<from $CLAUDE_SESSION_ID if available>"
project: "<project directory basename>"

task: |
  <one-paragraph description of what the user asked for>

files_modified:
  - path: "relative/path/to/file.md"
    action: "created|edited|deleted"
    summary: "what was changed and why"

decisions:
  - decision: "what was decided"
    rationale: "why"

progress:
  completed:
    - "step 1 description"
    - "step 2 description"
  current: "what step we're on now"
  next:
    - "next step 1"
    - "next step 2"

blocked:
  - item: "what's blocked"
    reason: "why"

open_questions:
  - "question that needs user input"

context_files:
  - "list of files that should be re-read on restore"

Show full SKILL.md (158 more words)Show less

Step 3: Confirm

Report to the user:

Checkpoint saved to .planning/checkpoint.yaml
- N files modified
- N decisions recorded
- Current step: [description]
- Next: [first next step]

Schema Rules

files_modified: Only files touched THIS session, not all project files
decisions: Only non-obvious choices. Skip mechanical decisions ("used latexmk" is obvious; "chose TWFE over CS estimator" is not)
context_files: List files that restore should re-read to reconstruct working context. Include CLAUDE.md, the plan file, and any files being actively edited
progress.current: Must be specific enough that restore can pick up exactly where we left off
Timestamps: Always ISO format, always local timezone

Multiple Checkpoints

Each checkpoint invocation overwrites the previous checkpoint. There is only one active checkpoint per project. If you need history, the git log preserves it.

Anti-Patterns

Do NOT write narrative prose — this is structured data for machine consumption
Do NOT include file contents — only paths and summaries
Do NOT checkpoint trivially (single-file edits with no decisions) — it's overhead without value
Do NOT use this instead of session-log — session logs are for humans, checkpoints are for restore

Files

Just SKILL.md in skills/checkpoint of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Checkpoint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Checkpoint compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Checkpoint this skillflonat/flonat-research	145	—	~999	Automated safety check: Pass	MIT	8 days ago
Memori Long-Term MemoryMemoriLabs/Memori	17k	—	~2k	Automated safety check: Notes	Custom licence	4 days ago
Planning with FilesOthmanAdi/planning-with-files	27k	—	~2.9k	Automated safety check: Pass	MIT	yesterday
User Thoughts Memorysickn33/agentic-awesome-skills	47k	1 repos	~2.5k	Automated safety check: Pass	MIT	yesterday
Session Handoff Documentthedotmack/claude-mem	97k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Planning With FilesOthmanAdi/planning-with-files	27k	—	~3k	Automated safety check: Pass	MIT	yesterday

Similar skills

Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
17k GitHub stars~2k tokensUpdated 4 days ago
Agent WorkflowsAuto-check: notes
Planning with Files
OthmanAdi/planning-with-files
Keeps a task plan, findings and progress log in markdown files on disk so long agent tasks survive context resets, with Gemini hooks and helper scripts.
27k GitHub stars~2.9k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
47k GitHub starsUsed in 1 repo~2.5k tokens
Agent WorkflowsAuto-check passed
Session Handoff Document
thedotmack/claude-mem
Writes a HANDOFF.md capturing goal, state, files, failed attempts and next steps so a fresh agent session can continue exactly where this one stopped.
97k GitHub stars~1.4k tokensUpdated today
Agent WorkflowsAuto-check passed
Planning With Files
OthmanAdi/planning-with-files
Keeps a task plan, findings and progress log as Markdown files in the project so long multi-step agent work survives context resets.
27k GitHub stars~3k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Harness Engineering
10xChengTu/harness-engineering
Set up and improve harness engineering (AGENTS.md, docs/, lint rules, eval systems, project-level prompt engineering) for AI-agent-friendly codebases.
102 GitHub starsUsed in 1 repo~1k tokens
Agent WorkflowsAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
145 GitHub stars~1.5k tokensUpdated 8 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
145 GitHub stars~4.4k tokensUpdated 8 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
145 GitHub stars~1.2k tokensUpdated 8 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
145 GitHub stars~488 tokensUpdated 8 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
145 GitHub stars~1.6k tokensUpdated 8 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
145 GitHub stars~2.8k tokensUpdated 8 days ago
Auto-check: notes

Questions about Checkpoint

What does Checkpoint do?

Save a compact continuation checkpoint so current work survives context compaction or a later session. Checkpoint is an agent skill from flonat/flonat-research. Save a compact continuation checkpoint so current work survives context compaction or a later session.

When should I use Checkpoint?

Checkpoint fits situations like: the active context is becoming long; work must pause without changing client; machine ownership.

How do I install Checkpoint in Claude Code?

Run `npx skills add flonat/flonat-research --skill checkpoint -a claude-code`. Or copy the skill folder (skills/checkpoint in flonat/flonat-research) into .claude/skills/checkpoint in your project. Claude Code loads it when a task matches its description.

How do I install Checkpoint in Codex?

Run `npx skills add flonat/flonat-research --skill checkpoint -a codex`. Or copy the skill folder (skills/checkpoint in flonat/flonat-research) into .agents/skills/checkpoint in your project. Codex loads it when a task matches its description.

Can I use Checkpoint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill checkpoint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/checkpoint, .gemini/skills/checkpoint, .github/skills/checkpoint and .opencode/skills/checkpoint in your project.

What does Checkpoint need to run?

Going by SKILL.md and its folder, Checkpoint needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(git*), Bash(date*), Bash(wc*), Glob.

Does Checkpoint access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Checkpoint safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Checkpoint use?

Checkpoint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Checkpoint use?

About 999 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Checkpoint?

Skills that share tags, products or a category with Checkpoint: Memori Long-Term Memory (MemoriLabs/Memori, 17k stars), Planning with Files (OthmanAdi/planning-with-files, 27k stars), User Thoughts Memory (sickn33/agentic-awesome-skills, 47k stars) and Session Handoff Document (thedotmack/claude-mem, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Checkpoint?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Checkpoint

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Checkpoint — Save Session State

When to Use

When This Skill Is Invoked

Step 1: Gather State

Step 2: Write Checkpoint

Step 3: Confirm

Schema Rules

Multiple Checkpoints

Anti-Patterns

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Related

Questions about Checkpoint