CtrlK
BlogDocsLog inGet started
Tessl Logo

bm-setup

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

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A thorough, actionable setup workflow with strong sequencing and verification, slightly verbose in the repeated sessionProfile/repository persistence rules.

Suggestions

Consolidate the sessionProfile and repository persistence rules (lines 110–130) into a single statement to reduce repetition.

The detailed interview field list and MCP-approval TOML config could optionally move to a reference file if the body grows further.

DimensionReasoningScore

Conciseness

Mostly efficient and skill-specific, but the sessionProfile/repository persistence rules are restated multiple times (e.g. lines 110–130) and could be consolidated; not padded with concepts Claude already knows.

2 / 3

Actionability

Provides exact JSON config blocks, copy-paste TOML snippets, specific commands like 'basic-memory hook status --harness codex --project-dir <repo-root>', and parameterized MCP tool calls — fully executable.

3 / 3

Workflow Clarity

Clear Preconditions → Interview → Apply → Seed Schemas → Verify sequence with an explicit Verify checkpoint and error-recovery feedback ('If any check errors, fix the project ref or hook launcher before finishing').

3 / 3

Progressive Disclosure

Self-contained setup skill with well-organized sections and no nested references; no bundle reference files are present (only assets/icon.svg), so well-organized inline sections satisfy the rubric.

3 / 3

Total

11

/

12

Passed

Description

82%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.

A specific, distinctive description with strong natural trigger terms, weakened only by the absence of an explicit 'when to use' clause.

Suggestions

Append a 'Use when…' clause naming natural triggers, e.g. 'Use when the user wants to connect Basic Memory to Codex or configure bm for a repo.'

Consider adding common phrasing variants like 'configure Basic Memory' or 'bm setup' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'mapping a Basic Memory project and seeding schemas' — plus the user/project-level choice, matching the multiple-specific-actions anchor rather than a single-domain description.

3 / 3

Completeness

Clearly states what the skill does, but lacks any 'Use when…' clause or equivalent explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

Uses the natural product names 'Basic Memory' and 'Codex' that a user would actually say when requesting this setup; no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The Basic-Memory-for-Codex niche with user/project scoping is specific and unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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.