agentleFS
Sign inStart free
omdenkar2-uiomdenkar2-ui/all-in-one/skills/aio-checkpoint/SKILL.md

aio-checkpoint

Skill0 starsChanged 31 days agoMITView on GitHub

Reconcile backend plan, units, review and verification evidence before advancing a pipeline stage.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the exact accepted source, plan and run ledger.

    line 12
  2. Distinctive:

    Run the plan gate before substantial implementation and the completion receipt checker before full completion.

    line 13

≈ “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

AIO Checkpoint

Reconcile backend plan, units, review and verification evidence before advancing a pipeline stage.

Protocol

  1. Read the exact accepted source, plan and run ledger. Match stable R/U/V IDs, revision/digests and checkpoint prerequisites to actual files/results.
  2. Run the plan gate before substantial implementation and the completion receipt checker before full completion. Add the mobile launch gate only when that release is in scope.
  3. Inspect semantic coverage and actual observations beyond helper output: expected behavior, current-head tests, independent review and observed delivery. Mechanical validation alone cannot authenticate commands.
  4. Advance only the checkpoint whose prerequisites and acceptance are satisfied. Failed, unavailable or stale evidence remains blocked/pending with a recovery action; a retry cap never changes its verdict.

Return and handoff

An observed stage decision and updated ledger/evidence, separate from a general reliability certification.

In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.

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