CtrlK
BlogDocsLog inGet started
Tessl Logo

bm-orient

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

60

Quality

69%

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

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

This is a well-structured, instruction-only orientation skill with explicit routing, drift-validation checkpoints, and lean prose that assumes Claude's competence. The main lever for improvement is tightening the few repeated repository-filter caveats and adding one concrete worked query example to reach fully copy-paste-ready actionability.

Suggestions

Consolidate the repeated 'apply metadata_filters={"repository": ...}' and 'never run an unscoped coding-session query' warnings into a single canonical rule referenced from each route, to trim repeated tokens.

Add one short concrete worked example of a topic-discovery query (e.g. an example read_note/search_note call with realistic arguments) to push actionability from concrete-but-instructional toward copy-paste-ready.

Optionally factor the query parameter table (type/status/repository/timeframe per route) into a compact reference block so each route section can stay purely about decision logic.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (it never explains what Basic Memory, MCP, or read_note are), with only minor repetition of the repository-filter caveats across routes that could be tightened slightly; it sits above the score-3 anchor but is not a 5 because those warnings recur and could be consolidated.

4 / 5

Actionability

It gives concrete, executable guidance (call read_note with project=<configured primaryProject>, apply metadata_filters={"repository": ...}, query type=task status=active) rather than vague direction; per the code_vs_instruction note, absence of code in an instruction-only skill is not penalized, but it stops short of fully copy-paste-ready examples.

4 / 5

Workflow Clarity

The process is explicitly sequenced (Resolve Configuration -> Choose One Recall Route -> Check Current State -> Present and Continue) with clear validation checkpoints: drift comparisons (same/different SHA, branch, repo), explicit error-reporting branches ('no credible match', 'setup incomplete'), and a feedback structure for ambiguous cases.

5 / 5

Progressive Disclosure

The skill is a single well-organized SKILL.md with clear section headers and no nested or buried references (the only bundle file is assets/icon.svg); per the simple-skill scoring note, well-organized single-file content with no need for external references scores 5.

5 / 5

Total

18

/

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 its niche and clearly distinct, but it lacks an explicit 'when to use' clause and natural trigger phrasings, capping both completeness and trigger-term quality at the midpoint. Adding a concrete 'Use when...' sentence with user-natural terms would lift it.

Suggestions

Add an explicit 'Use when...' clause naming the natural user moments that trigger this skill, e.g. 'Use when resuming an old thread, before substantial work in a repo, or when the user asks where things stand.'

Broaden trigger terms with user-natural synonyms ('Basic Memory checkpoint', 'resume session', 'where were we', 'catch up on context') alongside the technical jargon.

Optionally list the concrete sub-actions (read checkpoint note, run topic search, query active tasks/open decisions, report drift) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the Basic Memory domain and two concrete actions ('Resume from an exact Basic Memory checkpoint' and 'orient Codex from current graph and repository evidence'), matching the score-3 anchor of domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It clearly states the 'what' (resume/orient) but contains no explicit 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant specialized terms ('Basic Memory', 'checkpoint', 'Codex', 'graph', 'repository evidence') are present, but natural user-facing phrasings and synonyms are missing, so it sits at the 'some relevant keywords but missing common variations' anchor rather than full coverage.

3 / 5

Distinctiveness Conflict Risk

It targets a narrow Basic Memory/Codex niche with distinct triggers and minimal overlap risk, fitting the 'mostly distinct; minor overlap risk with closely related skills' anchor; not a 5 because the phrasing is not maximally trigger-specific.

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.

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.