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

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 high-quality, actionable procedural skill with explicit validation gates and concrete commands. It is dense rather than padded, though the dual-profile schema enumeration keeps conciseness and progressive disclosure just shy of the top anchor.

Suggestions

Move the coding-profile schema field list into a references file (e.g. coding-schema.md) and link to it, leaving the general profile inline, to improve progressive_disclosure and lighten the body.

Consider condensing the six pull_request_* field names into a compact table or shorthand list rather than a prose enumeration.

If a bundle directory is intended, add references/ so the bm-writing pointer and any schema detail resolve to real files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (raw git commands, no concept explanations), but the inlined general-vs-coding profile schemas and the full enumeration of six pull_request_* fields with rationale make it a dense reference document where a little detail could be delegated.	4 / 5
Actionability	Provides copy-ready, executable guidance throughout: exact commands (git status --short, git rev-parse HEAD, gh pr view --json), exact field names and types (note_type: coding_session, pull_request_number: "123"), and explicit routing rules covering general, coding, and PR cases.	5 / 5
Workflow Clarity	A clear Gather -> Write -> Confirm sequence with explicit validation checkpoints ("Do not claim a test passed unless you ran it", "Stop if the required coding fields cannot be proven") and error-recovery feedback (omit empty categories rather than placeholder text).	5 / 5
Progressive Disclosure	Well-organized into three clear sections with a one-level pointer to the bm-writing skill, but it is effectively a single monolithic file inlining both profile schemas; the coding-profile schema detail could arguably live in a reference file.	4 / 5
	Total	18 / 20 Passed

Description

100%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 is exemplary: third-person voice, concrete component list, explicit trigger clause, and a clearly distinct niche. It satisfies every anchor at the top of the scale.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete components of a checkpoint ("the story, changed files, verification, decisions, blockers, and the next action"), giving comprehensive coverage of what the skill saves rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both what ("Save a deliberate work checkpoint to Basic Memory...") and when ("Use when the user asks to checkpoint, wrap up, hand off, or remember the state of the work"), matching the concrete-trigger-phrase anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases a user would actually say ("checkpoint, wrap up, hand off, or remember the state of the work") with strong synonym coverage matching the comprehensive anchor.	5 / 5
Distinctiveness Conflict Risk	"Basic Memory" plus "deliberate work checkpoint" carves a clear niche with distinct triggers; the body further disambiguates it from the automatic PreCompact checkpoint, minimizing conflict risk.	5 / 5
	Total	20 / 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
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
Commit: a5fb68e

Reviewed: 3 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.