CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-notes

How to write well-structured Basic Memory notes: frontmatter, categorized observations, wiki-link relations, and knowledge-graph best practices. Use when creating or improving notes.

Quality

78%

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 ./skills/memory-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with executable tool examples, explicit search-before-create and checksum-validation checkpoints, and well-organized sections. Its weaknesses are duplicated bm_edit examples that waste tokens and heavy inlining of reference material that would be better split into separate files.

Suggestions

Deduplicate the bm_edit coverage: 'Granular Updates with bm_edit' and 'Editing an Existing Note' repeat the same commands and nearly identical insert_after_section examples — merge them into one section.

Move reference material (the relation-types table, memory-URL patterns, temporal-qualifier syntax, and the bm_edit command reference) into a references/ file, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add a single top-level workflow section (search for duplicates -> decide update vs. create -> write/edit -> verify via checksum) so the sequence is explicit in one place rather than spread across sections.

DimensionReasoningScore

Conciseness

The body is mostly tool-specific knowledge Claude would not already know, but it is noticeably redundant: the bm_edit insert_after_section example appears nearly verbatim in both 'Granular Updates with bm_edit' and 'Editing an Existing Note', the anatomy example is re-explained field-by-field in later sections, and phrases like 'Future-you (or your AI collaborator) will thank you' are padding. Mostly efficient, but several sections could be tightened or merged.

3 / 5

Actionability

Fully executable, copy-paste-ready calls for bm_write, bm_read, bm_search, bm_context, bm_move, and all seven bm_edit commands with real parameters, plus concrete syntax examples ('- [decision] Use REST over GraphQL for simplicity #api') and a relation-types table. Specific examples cover the common create/edit/move/search cases.

5 / 5

Workflow Clarity

Clear pre-flight check ('Always search Basic Memory before creating a new note'), an explicit decision tree (exists -> bm_edit, doesn't exist -> bm_write, unsure -> read first), and a genuine feedback loop for destructive edits ('A checksum conflict means someone changed the note after you read it. Read it again and redo the edit'). Validation is present so the destructive-operation cap does not apply, but there is no single unified top-level sequence, leaving minor gaps.

4 / 5

Progressive Disclosure

No bundle files exist, so everything — including reference material like the relation-types table, memory-URL patterns, the bm_edit command reference, and temporal-qualifier syntax — is inlined in a single ~415-line SKILL.md. Section headers keep it navigable (above the score-2 anchor), but content that clearly belongs in separate reference files is inline, matching the score-3 anchor.

3 / 5

Total

15

/

20

Passed

Description

75%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 strong, third-person description that clearly states what the skill does and when to use it, with several concrete capability components and natural trigger terms. Its main gap is that the 'when' clause and trigger vocabulary could be more varied and specific to reach top marks.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete components — 'frontmatter, categorized observations, wiki-link relations, and knowledge-graph best practices' — which exceeds the 1-2 actions of the score-3 anchor. It falls short of score 5 because coverage is not comprehensive (no mention of searching, editing existing notes, or memory URLs).

4 / 5

Completeness

Explicitly answers both: 'what' ('write well-structured Basic Memory notes: frontmatter, categorized observations, wiki-link relations...') and 'when' ('Use when creating or improving notes'). The trigger clause is present but generic, matching the score-4 anchor where 'when' could be more explicit with concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say — 'notes', 'Basic Memory', 'knowledge graph', 'creating or improving notes' — giving good keyword coverage. A few natural synonyms and variations are missing (e.g., 'knowledge base', 'note-taking'), keeping it below the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Basic Memory notes' carves out a clear niche with tool-specific triggers, so conflict risk is low. The broad 'creating or improving notes' clause could still overlap with generic note-taking skills, matching the score-4 anchor (mostly distinct, minor overlap risk).

4 / 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

skills/memory-notes/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.