checkpoint
Save a structured state snapshot before stopping or handing off.
Connecting the steps of a workflow
What it does
Produce a state snapshot that the next session (yours, or a collaborator's, or a fresh-context reboot) can resume from in under a minute. The narrative quality_reports/session_logs/ continues to live separately — /checkpoint writes the *structured* side: facts, file pointers, and next-actions.
Use when user says "checkpoint", "save state", "snapshot before I stop", "where am I", "wrap up
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
Lets your AI run any terminal command without asking, while the skill is in use
While the skill is working, Claude Code will not stop to ask before each terminal command. The permission ends when you send your next message.
How we know
SKILL.md line 1: “allowed-tools: ["Read", "Write", "Bash"]”. Read 2026-10-05, commit ae72617.
SKILL.md, line 1 ↗No serious risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit ae72617 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to pedrohcgs/claude-code-my-workflow: 2026-09-27 (8 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from pedrohcgs
All from this publisher →- adjudicate-review
Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without…
- audit-reproducibility
Before submission. Catches the "I updated the analysis but forgot to update Table 2" bug.
- blast-radius
Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format —…
- capture-environment
Before releasing a replication package to openICPSR, Zenodo, Dataverse, or a journal archive — the AEA Data Editor / DCAS standard…
- coauthor-brief
Generate a co-author / collaborator handoff brief for a multi-author, multi-machine project — summarizing what changed since the last brief (git delta),…
