CtrlK
BlogDocsLog inGet started
Tessl Logo

checkpoint

Save a local recovery packet from durable session state. Use when the user invokes /checkpoint, asks to preserve progress, or wants a safe restore point before risky or lengthy work.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/other/checkpoint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-organized instruction-only skill that tells Claude exactly what to capture and to deliver a non-overwriting packet with its path. Its main gap is the absence of storage location, format, and naming details that would make the recovery packet reliably restorable.

Suggestions

Specify where the recovery packet is written (e.g., a project-relative directory) and the file format/naming scheme so the restore side of the workflow is reliable.

Add an explicit verification step confirming the packet was written and is readable before reporting the path.

Split the body into two signaled sections (e.g., '## What to capture' and '## How to save') to make the distinct concerns easier to scan.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, listing only the fields to capture and the deliverable with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It gives a concrete list of what to capture (objective, plan, completed/pending work, evidence, workspace state, next action) and the output (report project-relative path), but omits key execution details such as where to write the packet, the file format, and naming convention.

3 / 5

Workflow Clarity

The sequence (capture fields, apply optional label, create a new non-overwriting packet, report path) is clear and unambiguous for a simple single-purpose skill, with "report its project-relative path" acting as the completion checkpoint; only a minor verify-that-it-was-written gap remains.

4 / 5

Progressive Disclosure

For a sub-50-line skill with no need for external references, a single clear heading and two well-organized paragraphs provide good structure, though the capture-versus-save concerns could be split into separate signaled sections for slightly cleaner navigation.

4 / 5

Total

16

/

20

Passed

Description

82%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, concise description that clearly answers both what the skill does and when to invoke it, with distinct, natural trigger terms. Its only weakness is that the capability list is a single high-level action rather than multiple concrete operations.

DimensionReasoningScore

Specificity

It names the domain ("recovery packet from durable session state") and one concrete action ("Save"), but does not enumerate the multiple sub-actions the body later details, so it sits at the 1-2 concrete actions anchor rather than comprehensive coverage.

3 / 5

Completeness

It explicitly states what ("Save a local recovery packet from durable session state") and when ("Use when the user invokes /checkpoint, asks to preserve progress, or wants a safe restore point"), matching the anchor requiring both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Phrases like "invokes /checkpoint", "asks to preserve progress", and "safe restore point" are natural user utterances with good synonym coverage, though a few common variants (e.g. "backup", "snapshot") are absent.

4 / 5

Distinctiveness Conflict Risk

The "/checkpoint" command trigger and "recovery packet" terminology carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

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
synthetic-sciences/openscience
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.