bm-writing

Apply the user-customizable writing standard for Basic Memory notes created or substantially revised by Codex. Use with bm-checkpoint, bm-decide, bm-remember, and other Basic Memory note-writing workflows.

Quality

81%

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

87%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 skill is a tight, well-organized writing standard with concrete templates and no token waste. Its only gap is the absence of an explicit sequenced workflow or validation checkpoints, though for a standard-of-style skill that is a minor issue.

Suggestions

Add a short ordered 'how to apply this standard' sequence (e.g. draft narrative spine -> add anchors -> distill observations -> add relations -> check evidence boundary) with an explicit final verification step.

Optionally surface a quick 'before you save' checklist consolidating the Evidence Boundary rules as a single validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, giving only writing-standard guidance without explaining concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Concrete, copy-paste-ready templates are given throughout (e.g. `- [category] fact`, `[decision]` observations, `- relation_type [[Target Note]]`, `- [branch] feat/bm-writing`), which is fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Content is organized into thematic sections (Voice, Tell The Story, Anchor, Semantic Layer, Evidence Boundary) but there is no sequenced workflow or explicit validation checkpoints; the multiple concerns are applied together without ordering, matching the 'steps listed but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	It is a single self-contained file with clear ## section organization and no nested external references, and no bundle files beyond an icon need navigation; structure is appropriate for its size.	3 / 3
	Total	11 / 12 Passed

Description

75%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 third-person, concise, and answers both what and when with an explicit trigger clause. Its main weakness is trigger phrasing built from sibling skill names rather than natural user keywords.

Suggestions

Add natural-language trigger terms a user would say (e.g. 'Use when writing or revising Basic Memory notes, project memory, or bm- notes') alongside the skill-name list.

Consider naming one or two more concrete actions (e.g. 'shape voice, structure observations, and anchor repo work') to lift specificity beyond a single 'apply' verb.

Dimension	Reasoning	Score
Specificity	Names the domain ("Basic Memory notes") and a core action ("Apply the user-customizable writing standard") but lists a single applied action rather than multiple concrete operations, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It states both what ("Apply the user-customizable writing standard for Basic Memory notes...") and when via an explicit "Use with..." trigger clause, satisfying the both what-and-when anchor.	3 / 3
Trigger Term Quality	"Basic Memory notes" is a relevant term, but the triggers are sibling skill names ("bm-checkpoint, bm-decide, bm-remember") rather than phrases a user would naturally say, so common natural-language variations are missing.	2 / 3
Distinctiveness Conflict Risk	The Basic Memory note-writing niche is specific and the triggers tie it to a named family of workflows, making it unlikely to fire for unrelated skills.	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-writing/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.