CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-checkpoint

Create an immutable Codex handoff in Basic Memory and return an exact bm-orient resume command.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/codex/skills/bm-checkpoint/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is an exceptionally actionable, well-sequenced instruction set with explicit validation gates, error-recovery loops, and exact tool-call syntax throughout — a model instruction-only skill. Its weaknesses are modest: some repetition around immutability rules could be tightened, and all ~220 lines live in SKILL.md with no reference-file split, so a large fraction of the detail is loaded even for simple invocations.

DimensionReasoningScore

Conciseness

The body is dense, directive prose with no explanations of concepts Claude already knows — every section issues concrete instructions. Minor tightening is possible: the immutability rule is stated multiple times ("Never edit, replace, or append to an earlier checkpoint", "Do not edit the previous immutable checkpoint", "Never resolve a collision by modifying the existing note") and some enumeration lists (e.g. the long "not a replacement for..." sentence) could be trimmed. This places it at 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level.

4 / 5

Actionability

The guidance is fully executable for an instruction-only skill: exact tool invocations ("bm_write with project=<...>, overwrite=False, and output_format=\"json\""), an exact title template with filename-safe timestamp rules, exact frontmatter field lists per profile, exact search filter syntax ("filters={\"agent\": \"codex\", \"session_id\": ...}"), an explicit resume-identifier fallback order ("permalink, file_path, then title"), and concrete error handling ("ALREADY_EXISTS" → retry with " - 2"). As the scoring notes allow, the absence of code in an instruction-only skill is not penalized when guidance is this actionable. Not below 5: no key execution detail is missing for the common cases.

5 / 5

Workflow Clarity

The Gather → Write → Confirm sequence is clearly ordered with explicit validation gates and feedback loops: "stop on any other action or error", "Only accept a successful result with action: created", "Stop if the required coding fields cannot be proven", a collision-retry loop with numeric suffixes, and a verify-before-linking checklist (search, page, deduplicate, confirm the exact agent/session_id pair, reject conflicts). This matches the anchor for clear sequence with explicit validation, error-recovery loops, and checklists. The write operation is guarded by non-overwrite enforcement, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

The bundle contains only assets/icon.svg — no references/ or scripts/ exist — and the entire ~220-line instruction set is inlined in SKILL.md with a single pointer to the external (non-bundle) `bm-writing` skill. Headers are well-organized, so it is not a 2 ('minimal structure'), but content that belongs in reference files (the general/coding frontmatter schemas, the same-chat linking procedure, the observations/relations syntax conventions) is all inline with no one-level-deep split, which fits 'some structure; content that should be separate is inline' better than 'most content appropriately placed'.

3 / 5

Total

17

/

20

Passed

Description

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

The description states a clear, distinctive 'what' with two concrete actions and tool-specific terms that make it highly distinguishable from other skills. However, it omits any 'when to use' trigger guidance and misses the natural trigger phrases (notably "checkpoint") that users would say, weakening both completeness and trigger discoverability.

Suggestions

Add a 'Use when...' clause to the description, e.g. "Use when the user asks to checkpoint, wrap up, hand off, or remember Codex work state" — the body already contains this trigger list, so surfacing it in the description would raise completeness from 3 to 5.

Include the natural trigger term "checkpoint" and common synonyms ("hand off", "wrap up", "save progress") in the description itself rather than only in the body, since users will phrase the request with those words.

Optionally name one more concrete capability (e.g. linking the checkpoint to earlier checkpoints in the same chat) to broaden the specificity coverage beyond the current two actions.

DimensionReasoningScore

Specificity

The description names the domain ("Codex handoff in Basic Memory") and two concrete actions ("Create an immutable... handoff" and "return an exact bm-orient resume command"), matching the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because two actions do not constitute 'several specific actions', and not a 2 because the actions are specific rather than generic.

3 / 5

Completeness

The 'what' is clear (create an immutable handoff note and return a resume command), but there is no 'Use when...' clause or equivalent trigger guidance in the description, which the guidelines explicitly cap at 3. Not a 4 because the 'when' is fully missing rather than merely under-specified.

3 / 5

Trigger Term Quality

Relevant keywords like "Codex", "Basic Memory", "handoff", and "resume" are present, but the natural phrases a user would actually say — "checkpoint", "wrap up", "remember the work state" — appear only in the body, not the description. Not a 4 because the primary natural trigger term ("checkpoint") is entirely absent from the description.

3 / 5

Distinctiveness Conflict Risk

"Codex", "Basic Memory", and "bm-orient" establish a clear niche with distinct triggers, giving minimal conflict risk with other skills. This matches the anchor for a clear niche with distinct triggers; no neighboring anchor fits better.

5 / 5

Total

14

/

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

basicmachines-co/basic-memory

Path

plugins/codex/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.