CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-checkpoint

An undo button for AI agent work: save the project before a risky change, see exactly what changed, roll back in one command. Use when: Save a checkpoint before a refactor, codemod, dependency upgrade or migration; See exactly which files an agent added, changed or deleted; Roll back the whole project or a single file, and undo the roll back.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is agent-checkpoint in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, honest guide with genuinely executable command examples and explicit safety mechanisms (dry-run, undoable restores) demonstrated through a realistic worked example. Its main weaknesses are redundancy (When-to-use and FAQ repeat other sections), promotional padding, and the absence of the script the whole document is written around.

Suggestions

Remove the 'When to use' section or the FAQ — both largely restate the frontmatter description and the 'Safe by design'/'Known limitations' sections; keeping one consolidated copy would cut tokens without losing information.

Trim the promotional footer and 'Free skill by Nex AI' banner lines; they add no guidance value and compete with the context budget.

Add a short 'General workflow' sequence (save before a risky change -> diff after -> dry-run -> restore) alongside the worked example, plus one line on how to obtain and invoke checkpoint.py, so the process does not have to be inferred from the example.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the 'When to use' bullets near-verbatim duplicate the frontmatter description, the FAQ re-answers points already made in 'Safe by design' and 'Known limitations', and promotional lines ('Free skill by Nex AI', 'More skills, including the paid catalog') pad the token budget. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trimming bar of 4.

3 / 5

Actionability

Concrete, realistic command examples with output are shown for every subcommand (save -m, diff --patch, restore --dry-run, restore --path), covering the common cases. It falls short of fully copy-paste-ready because no invocation path or installation guidance is given and the script is explicitly 'not in this folder'.

4 / 5

Workflow Clarity

The save -> diff -> selective restore -> undo flow is demonstrated end-to-end with explicit validation (`restore 1 --dry-run`) and a built-in feedback loop ('Every restore is undoable: it checkpoints the current state first'), so the destructive-operation cap does not apply. It is not a 5 because the general workflow is only implied by the example rather than stated as a sequence, with no error-recovery guidance for failed restores.

4 / 5

Progressive Disclosure

Sections are clearly organized with headers and no nested references, and there is no wall of inline reference material. However the body exceeds the simple-skill threshold (~110 lines) with the extended example transcript and hook details that could be split out, and the described checkpoint.py script is missing from the skill folder entirely, leaving minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states what the skill does and when to use it, with concrete, third-person action statements and natural trigger phrases tied to real agent scenarios. The only gaps are a few missing common synonyms ('revert', 'snapshot') and slight overlap risk with generic rollback/backup tooling.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'save the project before a risky change, see exactly what changed, roll back in one command', 'Roll back the whole project or a single file, and undo the roll back' — comprehensively covering the tool's save/diff/restore/selective-restore/undo capabilities. It clearly matches the 'multiple specific concrete actions; comprehensive coverage' anchor, with no capability gaps that would place it at 4.

5 / 5

Completeness

It explicitly answers both parts: the 'what' opens with 'An undo button for AI agent work: save the project... see exactly what changed, roll back in one command', and the 'when' is an explicit 'Use when:' clause with three concrete trigger scenarios. This matches the top anchor exactly and is clearly above the 4 anchor's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — 'refactor, codemod, dependency upgrade or migration', 'which files an agent added, changed or deleted', 'roll back' — giving good keyword coverage. It stops short of the 5 anchor because common synonyms such as 'revert', 'snapshot', or 'undo changes' are missing.

4 / 5

Distinctiveness Conflict Risk

'An undo button for AI agent work' and 'checkpoint' carve out a clear, distinct niche, but the generic actions 'roll back' and 'undo' create minor overlap risk with closely related git-safety or backup skills. This fits 'mostly distinct; minor overlap risk' rather than the 5 anchor's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-dev-essentials/skills/agent-checkpoint/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.