bm-status

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

Quality

83%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exemplary concise, actionable diagnostic playbook with concrete commands, explicit validation checkpoints, and a clear output shape. No significant weaknesses relative to the rubric.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding or explanation of known concepts; every line is operational guidance.	3 / 3
Actionability	It provides copy-paste-ready commands, concrete config paths, specific query types, and a fixed output template, all fully executable.	3 / 3
Workflow Clarity	A clear numbered Gather/Present sequence with explicit validation checkpoints (launcher fallbacks, repo-scope guard, config-vs-hook mismatch, inbox warning) provides feedback loops for error recovery.	3 / 3
Progressive Disclosure	This under-50-line single-purpose skill is well-organized into Gather and Present sections with no external references needed, which satisfies the simple-skill exception for a top score.	3 / 3
	Total	12 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 distinct, clearly scoping a Basic Memory for Codex diagnostic skill. Its main weakness is the absence of an explicit 'Use when...' trigger and reliance on internal jargon over natural user phrasing.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants a Basic Memory for Codex status check or asks about hook health, checkpoints, or active tasks.'

Replace some internal jargon with natural terms users would say (e.g. add 'status report', 'health check') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ('configuration, reachability, hook expectations, recent Codex checkpoints, and active tasks'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but provides no 'when to use it' trigger, and the guidelines cap completeness at 2 for a missing 'Use when...' clause.	2 / 3
Trigger Term Quality	It uses product-internal jargon ('hook expectations', 'Codex checkpoints') and lacks a natural 'Use when...' phrase a user would say, so it lands at 'some relevant keywords but missing common variations' rather than full natural-term coverage.	2 / 3
Distinctiveness Conflict Risk	It targets a specific named product (Basic Memory for Codex) with a distinct niche, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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/codex/skills/bm-status/SKILL.md
Commit: cb95e59

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