agentleFS
Sign inStart free
VoidLight00VoidLight00/jev-for-claude/skills/compact-checkpoint/SKILL.md

compact-checkpoint

Skill0 starsChanged 37 days agoMITView on GitHub

Create a compact, evidence-grounded checkpoint before context loss or handoff.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Create a compact checkpoint for: $ARGUMENTS

    line 7
  2. Distinctive:

    Do not copy secrets, full conversations, large logs, or unverified assumptions.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Create a compact checkpoint for: $ARGUMENTS

Include only:

  • objective and non-negotiable constraints;
  • verified facts and their evidence locations;
  • files changed and commands actually run;
  • decisions made and rejected alternatives;
  • open blockers, unknowns, and the next three actions;
  • safety or privacy boundaries that must survive handoff.

Do not copy secrets, full conversations, large logs, or unverified assumptions. Keep the checkpoint short enough to re-read before acting.

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