CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-setup

Set up Basic Memory for Codex at user or project level by mapping a Basic Memory project and seeding schemas.

Quality

74%

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-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, highly actionable setup procedure with concrete tool calls, copy-ready config blocks, confirmation checkpoints, and an explicit verification phase. Its main weaknesses are mild redundancy around sessionProfile/repository persistence rules and a description/frontmatter trigger gap rather than anything in the body itself.

Suggestions

De-duplicate the sessionProfile/repository persistence guidance, which is stated in the user-level paragraph and again in the following 'Persist sessionProfile explicitly...' paragraph.

Name the exact search tool and arguments for the schema verification step (e.g. bm_search(...)) so it is copy-paste executable like the other steps.

Consider moving the long Interview field-by-field spec into a references file and linking it, keeping the core flow lean in SKILL.md.

DimensionReasoningScore

Conciseness

The body is directive and dense with no explanations of concepts Claude already knows, but it has minor redundancy that could be trimmed: the sessionProfile/repository persistence rules are stated twice and the capture-events default is explained in both the Interview and Apply sections. Not a 5 because those repeats cost tokens without adding information.

4 / 5

Actionability

Provides concrete MCP calls (bm_project(command="list"), bm_write with directory and note_type), CLI commands (basic-memory hook status --harness codex --project-dir <repo-root>), and complete copy-adaptable JSON and TOML blocks. Minor gaps remain, e.g. 'Search the primary project for type=schema with page size 10' does not name the exact tool call to use.

4 / 5

Workflow Clarity

Clear sequence (Preconditions, Interview, Apply, Seed Schemas, Verify) with explicit validation steps in Verify and an error-recovery loop ('If any check errors, fix the project ref or hook launcher before finishing'), plus confirmation checkpoints before every write and config edit. Matches the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

Sections are well organized and the bundle is self-contained (only assets/icon.svg, unreferenced), with external references (<plugin-root>/schemas/) one level deep and clearly signaled. Not a 5 because the long inline interview spec could arguably live in a reference file and the schema filenames (coding-session.md, decision.md, task.md) are named but not linked or listed.

4 / 5

Total

17

/

20

Passed

Description

53%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 to a named product and harness and states a clear 'what', but it lacks any 'when to use' trigger guidance and omits several of the skill's actual capabilities. Adding an explicit 'Use when...' clause with natural trigger terms would raise both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user wants to set up, configure, or initialize Basic Memory for Codex, or mentions bm, memory setup, or a first-time Basic Memory run.'

Broaden trigger-term coverage with natural synonyms users would say: 'bm', 'configure', 'initialize', 'install/setup', 'memory'.

Mention one or two more concrete capabilities that the body performs (e.g. choosing MCP approval mode, verifying the mapping) to improve coverage without padding.

DimensionReasoningScore

Specificity

Names the domain ('Basic Memory for Codex', 'user or project level') and two concrete actions ('mapping a Basic Memory project and seeding schemas'), but omits several capabilities the skill actually performs (interview, config writing, MCP approval setup, verification), so coverage is not comprehensive as the score-4 anchor requires.

3 / 5

Completeness

Has a clear 'what' (set up at user or project level, map a project, seed schemas) but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes some relevant keywords ('Basic Memory', 'Codex', 'set up') but misses natural variations and synonyms users would say, such as 'bm', 'configure', 'initialize', 'checkpoint', or 'memory'.

3 / 5

Distinctiveness Conflict Risk

Naming both the product ('Basic Memory') and the harness ('Codex') carves a distinct niche with minimal conflict risk, but sibling plugin skills (e.g. bm-checkpoint, bm-share) create minor overlap risk and no explicit triggers are given to disambiguate, so it is not a 5.

4 / 5

Total

13

/

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/codex/skills/bm-setup/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.