CtrlK
BlogDocsLog inGet started
Tessl Logo

bm-status

Report the Basic Memory for Codex configuration, reachability, hook expectations, recent Codex checkpoints, and active tasks.

62

Quality

72%

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

Fix and improve this skill with Tessl

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

Quality

Content

82%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 highly actionable and well-sequenced for a read-only diagnostic, with real commands, fallback handling, and a concrete output template. Conciseness and progressive disclosure are strong but not maximal, leaving minor room to tighten phrasing.

DimensionReasoningScore

Conciseness

The body is lean and directive ('Do not over-investigate') and its asides convey non-obvious domain facts (e.g. 'inbox counts are global across supported harnesses'), with only a few phrasings that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands with explicit fallback chains ('basic-memory --version' → 'bm --version' → 'uvx --prerelease=allow basic-memory --version'), an exact hook-status command, concrete query predicates, and a full presentation template.

5 / 5

Workflow Clarity

A clear numbered Gather (1–5) → Present sequence with edge-case checkpoints (mismatch reporting, scoping guards, launcher fallbacks); it lacks a full validate→fix→retry loop, but the operation is read-only so none is strictly required.

4 / 5

Progressive Disclosure

A single self-contained file with clean 'Gather' and 'Present' sections and no nested references; the only bundle asset is an icon, so structure is good though slightly above the under-50-line simple-skill threshold.

4 / 5

Total

17

/

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 is specific and clearly occupies a distinct niche, but it omits any 'Use when...' trigger guidance and relies on somewhat narrow domain keywords, which limits completeness and trigger-term quality. Adding an explicit activation clause and a few natural synonyms would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when checking Basic Memory for Codex health, configuration, or hook status.'

Add natural trigger synonyms users might say, such as 'health check', 'diagnostics', or 'Basic Memory status'.

Mention 'open decisions' alongside checkpoints and tasks so the description matches the full scope covered in the body.

DimensionReasoningScore

Specificity

Names the domain (Basic Memory for Codex) and lists several concrete reportable items — 'configuration, reachability, hook expectations, recent Codex checkpoints, and active tasks' — under the verb 'Report', with minor gaps such as the 'open decisions' that appear only in the body.

4 / 5

Completeness

It gives a clear 'what' (what to report) but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant domain keywords ('Basic Memory', 'Codex', 'status', 'checkpoints', 'tasks') are present, but common natural variations or synonyms a user might actually say ('health check', 'diagnostics', ' Basic Memory status') are missing.

3 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — a status diagnostic for the specific Basic-Memory-for-Codex integration — with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
basicmachines-co/basic-memory
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.