CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-checkpoint

Save a deliberate work checkpoint to Basic Memory with the story, changed files, verification, decisions, blockers, and the next action. Use when the user asks to checkpoint, wrap up, hand off, or remember the state of the work.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is an exemplary instruction-only skill: lean, fully concrete, with a clearly sequenced three-phase workflow, explicit honesty and stop-condition checkpoints, and precise schemas for the written note. Nothing is padded, buried, or missing for the task it describes.

DimensionReasoningScore

Conciseness

The body is dense and directive throughout: it supplies exact commands ('git status --short', 'git rev-parse --show-toplevel', 'gh pr view --json ...') instead of explaining concepts Claude already knows, and even the intricate config-precedence and legacy-field rules are non-obvious operational specifics that earn their tokens.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: the bm_write call has every parameter specified (title, directory, tags, note_type, exact frontmatter keys), section names and observation tags are given verbatim, and git/gh commands are concrete and copy-paste ready.

5 / 5

Workflow Clarity

A clear Gather -> Write -> Confirm sequence is backed by explicit validation checkpoints ('Do not claim a test passed unless you ran it', 'Stop if the required coding fields cannot be proven'), a gather checklist, and conditional handling ('omit those fields when no PR exists'); it is a single-note write, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: all inline content is per-invocation operational detail, sections (Gather/Write/Confirm) are well-organized and easy to navigate, and the single external pointer (the bm-writing skill) is clearly signaled and one level deep.

5 / 5

Total

20

/

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 clearly states a concrete single-purpose capability, lists exactly what the checkpoint contains, and pairs it with an explicit 'Use when' clause of natural trigger phrases. The only minor weaknesses are a few missing natural trigger synonyms and slight overlap risk from generic wrap-up/hand-off phrasing.

DimensionReasoningScore

Specificity

The description names the destination tool ('Save a deliberate work checkpoint to Basic Memory') and comprehensively enumerates six concrete content components ('the story, changed files, verification, decisions, blockers, and the next action'), matching the comprehensive-coverage anchor with no noticeable gap.

5 / 5

Completeness

It explicitly answers both 'what' (save a checkpoint to Basic Memory with the listed contents) and 'when' via a concrete 'Use when the user asks to checkpoint, wrap up, hand off, or remember the state of the work' clause.

5 / 5

Trigger Term Quality

Trigger phrases 'checkpoint, wrap up, hand off, or remember the state of the work' are natural user phrasings with good synonym coverage, but a few natural variants (e.g. 'save progress', 'handover', 'brief the next session') are missing, fitting the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Basic Memory' target and specific content list give it a clear niche, but the somewhat generic 'wrap up' and 'hand off' triggers create minor overlap risk with other summary/handoff skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

basicmachines-co/basic-memory

Path

plugins/claude-code/skills/bm-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.