session-checkpoints

Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 concise, well-sequenced skill body with strong validation checkpoints and an error-recovery loop. Its main weakness is integrity: the creation workflow depends on a CHECKPOINT-TEMPLATE.md that is referenced but not actually bundled.

Suggestions

Add the missing ./CHECKPOINT-TEMPLATE.md to the bundle (or inline the template structure) so the canonical creation step is fully executable.

Include a short example of the checkpoint file's expected contents so Claude can reconstruct one even if the template is unavailable.

Clarify the 'Phase boundaries that warrant a checkpoint: load the decomposition skill' line — state what to do after loading it rather than leaving the action implicit.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence — no concept explanations, no padding, every line is actionable guidance or a trigger rule, matching the anchor 5 lean-and-efficient example.	5 / 5
Actionability	Concrete commands (git status, git branch, cat, git log --oneline -20) and specific paths make most steps executable, but the core creation step depends on a referenced CHECKPOINT-TEMPLATE.md whose content is not provided — a minor gap keeping it below fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	Creating and Resuming are clearly sequenced with explicit validation checkpoints ("Verify: cat ...; confirm listed files exist", "confirm you are on correct branch", "verify files match expected state") plus an error-recovery feedback loop for a missing/corrupt checkpoint, matching anchor 5.	5 / 5
Progressive Disclosure	Section structure is good and the CHECKPOINT-TEMPLATE.md reference is one-level-deep and clearly signaled, but that referenced file does not exist in the bundle (references/scripts/assets are absent), so the disclosure path is broken in practice — a reader following it hits a dead end.	3 / 5
	Total	17 / 20 Passed

Description

91%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, third-person description that clearly states both capability and trigger conditions with natural phrasing and synonyms. It is comprehensive on triggers and completeness, with only minor overlap risk and slightly limited action-verb variety.

Dimension	Reasoning	Score
Specificity	Names the domain ("session state") and lists concrete state components — "task progress, file changes, delegation history" — plus the save/restore actions, but only two action verbs keep it just short of the comprehensive multi-action anchor 5.	4 / 5
Completeness	Explicitly answers what ("Saves, restores session state including...") and when ("Use when...") with concrete trigger phrases, matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	"Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work" gives comprehensive natural trigger phrases, including the synonym pair "resuming interrupted work" / "picking up where you left off".	5 / 5
Distinctiveness Conflict Risk	The checkpointing niche and "checkpointing current work" trigger are distinct, but "file changes" and "delegation history" create minor overlap risk with git and delegation skills, so it is mostly distinct rather than fully niche-clear.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/session-checkpoints/SKILL.md
Commit: f297837

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.