CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bm-orient

Resume from an exact Basic Memory checkpoint or orient Codex from current graph and repository evidence.

Quality

80%

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-orient/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-engineered, instruction-only skill body: it prescribes an unambiguous four-phase workflow with explicit validation and failure-reporting checkpoints, and its guidance is concrete down to exact tool calls, filter syntax, and config keys. The only real costs are mild repetition of the setup-incomplete/repository-filter rules across routes and the absence of the search tool's exact call signature.

DimensionReasoningScore

Conciseness

The body is dense and procedural with no explanation of concepts Claude already knows; every section gives operational rules. It is not a 5 because the coding-session repository-filter rule and the "report setup is incomplete" instruction are each repeated nearly verbatim across the three routes and could be consolidated into the Resolve Configuration section.

4 / 5

Actionability

Gives concrete, executable guidance: exact calls like `bm_project(command="list")`, `bm_read` with `project=`, literal filter syntax `filters={"repository": "<configured repository>"}`, named config keys, and concrete note types and statuses. It falls short of anchor 5 because the search tool is only referred to as "note/search calls" without its exact name or parameter signature, leaving one common case not fully copy-paste ready.

4 / 5

Workflow Clarity

A clear four-phase sequence (Resolve Configuration → Choose One Recall Route → Check Current State → Present and Continue) with explicit decision points: the 0/1/multiple match handling ("show at most three ... then wait for the user to choose"), the drift-comparison matrix keyed on repository/SHA/branch/cwd, and explicit instructions to report unprovable comparisons. Validation checkpoints and error-recovery reporting are present throughout, matching the anchor-5 example's structure.

5 / 5

Progressive Disclosure

The body is self-contained with well-organized, clearly headed sections and no nested or buried references; the only bundle asset (assets/icon.svg) is appropriately non-procedural. It is not a 5 because the skill exceeds the ~50-line threshold where a fully inline single file earns the top score, and the per-route rules (exact checkpoint, topic discovery, current repository) are long enough that they could plausibly live in one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

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

A specific, distinctive description that clearly states what the skill does in third person with concrete, niche-appropriate terminology. Its main weakness is the absence of any explicit "when to use" trigger guidance, which both caps completeness and leaves some natural trigger phrases unsurfaced.

Suggestions

Add an explicit trigger clause, e.g. "Use when resuming an old thread, before substantial work in a repo, or when the user asks where things stand" — the body already contains this guidance, so surfacing it in the description would lift completeness from 3 to 5.

Include one or two natural user phrasings such as "continue where we left off" or "catch up on context" to broaden trigger-term coverage.

Optionally mention the drift-checking and orientation-summary outputs (e.g. "compares checkpoint state against live repository evidence") to round out the action list toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names two precisely-qualified concrete actions — "Resume from an exact Basic Memory checkpoint" and "orient Codex from current graph and repository evidence" — with domain specifics. It falls just short of anchor 5, whose examples list multiple (3+) distinct actions; it also exceeds anchor 3, which expects generic or less comprehensive action descriptions.

4 / 5

Completeness

The "what" is clear (resume from a checkpoint, orient from graph and repository evidence), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description itself, which caps completeness at 3. It is not a 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Includes natural terms a user would say — "resume", "checkpoint", "orient", "repository" — plus the niche names "Basic Memory" and "Codex". A few natural variations ("continue", "catch up", "where we left off") are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Exact Basic Memory checkpoint" and "Codex" orientation define a clear niche with distinct triggers, minimal overlap with other skills. Matches anchor 5; anchor 4 would imply residual overlap with closely related skills, which is not the case here.

5 / 5

Total

16

/

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-orient/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.