CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-status

Show the Basic Memory plugin's current state for this project — active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable.

Quality

83%

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

SKILL.md
Quality
Evals
Security

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 tight, highly actionable diagnostic procedure: exact commands and tool calls, a fixed output template, and thorough fallback handling for every failure mode. The only minor improvements are trimming a couple of verbose spots and deciding whether the config-key/default enumeration belongs inline or in a small reference file.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no background concept explanations, just procedure — but a few spots could be tightened: step 2's config-precedence prose ('do not trim it, expand ~, or treat an empty value as unset') runs long, and the instruction to pass the project's external ID as `project` is stated twice. This is 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place top anchor.

4 / 5

Actionability

Fully executable throughout: exact launcher commands with fallbacks (`basic-memory --version`, then `bm --version`, then `uvx --prerelease=allow basic-memory --version`), a precise hook command (`basic-memory hook status --harness claude --project-dir <project-root>`), concrete MCP calls with argument syntax (`bm_search` with `filters={"type": "session"}`, `page_size` 5), and a copy-paste-ready output template. As an instruction-only skill, its guidance is concrete and complete with no gaps.

5 / 5

Workflow Clarity

A clear numbered gather sequence (CLI reachability → configuration → hook health → checkpoints → tasks) followed by a fixed presentation template, with explicit error-recovery branches: unavailable launchers degrade gracefully ('mark these fields unavailable and continue'), config mismatches are surfaced, undetermined values are written as '—' rather than failing the report, and empty-state/warning rules are spelled out. The read-only diagnostic involves no destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and clean two-section organization, and everything inlined is needed at invocation time. It sits just above the rubric's under-50-line simple-skill threshold, and the inline enumeration of `basicMemory` config keys with defaults is borderline reference material, so this fits 'good structure; most content appropriately placed; minor organization gaps' rather than a flawless 5.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific, well-scoped description that clearly states what the skill reports and occupies a distinct niche, but it lacks any 'Use when...' trigger guidance (capping completeness at 3) and misses a few natural synonyms users might say. Adding an explicit trigger clause referencing status/diagnostic requests would round it out.

Suggestions

Add a trigger clause, e.g. 'Use when the user asks for Basic Memory status, wants to check capture/checkpoint health, or suspects the plugin is misconfigured.'

Include natural synonyms users might say — 'bm status', 'Basic Memory diagnostics', 'check Basic Memory' — to broaden trigger-term coverage.

Optionally mention the hook/inbox health fields (pending envelopes, last flush) that make up a significant part of the report, closing the minor coverage gap.

DimensionReasoningScore

Specificity

The description enumerates concrete reportable items — "active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable" — going well beyond naming the domain, but it omits several fields the skill actually reports (shared inbox state, pending envelopes, active tasks), so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The 'what' is clear and concrete (shows the plugin's current state with enumerated fields), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because a 'when' element is entirely absent rather than merely imprecise, and not a 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

It includes natural terms a user would say — "Basic Memory", "status"/"current state", "checkpoints" — but misses common synonyms and variations such as "bm status", "diagnostics", or "capture health". This matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The description is firmly scoped to the "Basic Memory plugin" — a proper-noun niche with distinct terms (capture folders, session checkpoints, output style) — making it clearly distinguishable from other skills with minimal risk of triggering the wrong one.

5 / 5

Total

16

/

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