CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-capture

Capture a working thread's current state into one coherent Basic Memory note; on re-capture, rewrite it in place. Use mid- or end-of-thread when decisions, insights, or context are worth keeping.

Quality

85%

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

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 highly actionable, well-sequenced skill whose workflow for the destructive overwrite path includes checksum validation and a conflict-recovery loop, backed by concrete MCP calls and complete worked examples. The main cost is redundancy: the synthesis philosophy and best practices repeat content stated earlier, and the long inline examples could move to a reference file.

Suggestions

Trim the Best Practices section or fold it into earlier sections — items 1-3 restate the Purpose/Synthesis Rules nearly verbatim, cutting ~10 lines of repeated guidance.

State the synthesize-don't-append rule once (in Synthesis Rules) and trim its restatements in Purpose, the examples' "Notice that" list, and Best Practices.

Move one or both full example notes into a references/examples.md file and keep a one-line pointer plus the key "notice" points inline, slimming the SKILL.md body.

DimensionReasoningScore

Conciseness

The core synthesize-don't-append rule is restated four-plus times — in Purpose ("capture the current state of understanding, not the history"), Synthesis Rules ("synthesize, don't append"), the examples' "Notice that" list, and again in Best Practices ("Capture the current state, not the history", "Synthesize, don't log") — and the Best Practices section largely restates earlier sections. Mostly efficient with no beginner-concept padding, but noticeably tightenable, fitting the 3 anchor.

3 / 5

Actionability

Fully executable MCP calls are given for every path — bm_search with filters vs query, bm_read with output_format="json", and bm_write with overwrite=True and expected_checksum=existing["checksum"] — plus a complete note template and two end-to-end worked examples covering create and update. Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The Decision Flow is a clearly numbered sequence with branching for match/no-match, guards the destructive overwrite with expected_checksum, and includes an explicit error-recovery loop ("A REVISION_CONFLICT error means another session changed the note… read it again and re-synthesize"). This matches the top anchor: explicit validation steps with feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single well-sectioned document with clear headers and easy navigation. The two full example notes (~90 lines of the body) are inlined and could be split into a separate examples file, which is a minor organization gap — the 4 anchor rather than 5, which expects content appropriately split across referenced files.

4 / 5

Total

17

/

20

Passed

Description

82%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 description that explicitly answers both what and when in third person, anchored to a specific tool with distinctive in-place-rewrite behavior. Its only weakness is modest action coverage and a few missing user-side synonyms like "save" or "remember".

DimensionReasoningScore

Specificity

"Capture a working thread's current state into one coherent Basic Memory note" and "on re-capture, rewrite it in place" name the domain with two concrete actions, but coverage isn't comprehensive — the body's search, checksum, and note-structuring behavior is absent. This matches the 1-2-concrete-actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

The what is explicit ("Capture a working thread's current state into one coherent Basic Memory note; on re-capture, rewrite it in place") and the when is an explicit trigger clause ("Use mid- or end-of-thread when decisions, insights, or context are worth keeping") with concrete conditions. Both are clearly and concretely answered, matching the top anchor rather than the 4 anchor where the when is only loosely specified.

5 / 5

Trigger Term Quality

Natural terms like "Capture", "decisions, insights, or context", and "mid- or end-of-thread" cover the main ways a user would voice this need. A few common synonyms ("save this", "remember", "summarize the session") are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is pinned to a named tool ("Basic Memory note") with distinctive mechanics (in-place rewrite on re-capture, thread-timed triggers), giving minimal overlap with generic note-taking or memory skills.

5 / 5

Total

17

/

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