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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/claude-code/skills/bm-status/SKILL.md

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.

The body is an excellent, fully executable diagnostic procedure: exact commands, precise MCP query parameters, a literal output template, and explicit fallbacks for unavailable components. Its only minor weaknesses are a slightly wordy config-precedence paragraph and its length relative to the simple-skill threshold.

Dimension	Reasoning	Score
Conciseness	The body is lean and instructional throughout — "This is a quick diagnostic — gather the facts and lay it out; don't over-investigate" — with no concept explanations or padding, assuming Claude's competence. Anchor 4 rather than 5 only because the config-precedence paragraph ("do not trim it, expand `~`, or treat an empty value as unset") is slightly wordier than strictly necessary.	4 / 5
Actionability	Everything is copy-paste ready: exact commands (`basic-memory --version`, `uvx --prerelease=allow basic-memory --version`, `basic-memory hook status --harness claude --project-dir <project-root>`), fully parameterized `search_notes` calls with `metadata_filters` and `page_size`, and a literal output template. Anchor 5 — concrete commands cover the common cases, including the coding-profile variant.	5 / 5
Workflow Clarity	A clear five-step Gather sequence flows into a Present template, with explicit error-recovery fallbacks ("If no launcher resolves... mark these fields unavailable and continue", "write '—'... rather than failing the whole report") and a canonical-vs-merged config mismatch check. Anchor 5; the read-only diagnostic nature means the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist and the skill is a single cohesive self-contained procedure with clean `## Gather` / `## Present` sections and an integral output template — nothing is misfiled or buried. Anchor 4 rather than 5 because at ~93 lines it exceeds the under-50-line simple-skill case where sections alone would suffice.	4 / 5
	Total	18 / 20 Passed

Description

62%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 has a clear, specific "what" with a distinct niche and enumerated reportable fields, but it completely lacks "when to use" trigger guidance and natural trigger-term variations, capping both completeness and trigger quality. It is a solid but incomplete description per this rubric.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for Basic Memory status, a plugin health check, or a diagnostic of capture/checkpoint behavior."

Include natural trigger-term variations users would actually say — "status", "diagnostic", "health", "check Basic Memory" — alongside the existing field names.

Optionally mention hook-inbox health and active-task counts so the description's claimed coverage matches what the skill actually reports.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete reportable fields ("active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable") around a single clear action ("Show the Basic Memory plugin's current state"). It lists several specific items with only minor gaps — e.g. hook-inbox health and active-task counts from the body are not surfaced — placing it at anchor 4 rather than 5.	4 / 5
Completeness	The "what" is clear and field-specific (show the plugin's current state with the listed fields), but there is no "Use when..." clause or any trigger guidance, so per the judging guideline completeness is capped at 3. Not 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Contains some relevant natural keywords ("Basic Memory", "current state", "checkpoints", "capture folders") but misses common variations and phrasings users would naturally say, such as "status", "diagnostic", or "health check". Fits anchor 3; not 4 because several natural trigger terms are absent.	3 / 5
Distinctiveness Conflict Risk	"Basic Memory plugin's current state for this project" carves out a clear niche tied to a distinct product name, with minimal risk of triggering for the wrong skill. Matches anchor 5; not 4 because there is no meaningful overlap with other skill domains.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 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
Commit: 194afe1

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