CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-reflect

Sleep-time reflection: review recent Basic Memory activity and fold lasting decisions, lessons, and facts into the notes they belong in. Run 1-2x daily, on a heartbeat, or when asked.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/memory-reflect/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.

The body is a strong, example-driven process guide: executable API calls with parameters, an explicit decision rubric, and genuine error-recovery loops for batch edits. Its only notable gaps are the missing bm_write example and the absence of any bundle structure to offload detail into.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific: code blocks carry real parameters, the keep/skip table compresses decision criteria, and there is no re-explanation of concepts Claude already knows. Only minor trimming candidates exist, such as the 'Inspired by sleep-time compute' framing sentence, keeping it just below the lean anchor-5 bar.

4 / 5

Actionability

Provides executable bm_list/bm_recent/bm_read/bm_search/bm_edit calls with concrete arguments, pagination instructions, checksum conflict handling, and a complete reflection-note template. The one gap is that bm_write is named as the tool for creating new notes but never shown with an example call, so guidance is not fully copy-paste ready across all steps.

4 / 5

Workflow Clarity

Four steps are clearly sequenced (gather, decide, place, record) with explicit validation and feedback loops for a batch note-editing operation: read every changed note before judging, pass expected_checksum so edits apply only to the revision read, and on checksum conflict re-read and re-decide. Edge cases are also handled — skipping already-reviewed notes, the 365-day lookback limit, and flagging uncertain items with '(needs confirmation)'.

5 / 5

Progressive Disclosure

No bundle files exist, and the single-file layout is well organized with clear sections (Project scope, When to Run, Process, Guidelines, Related skills), deferring note-format detail to the memory-notes skill one level deep. It is not a 5 because the ~160-line body keeps all process detail inline and the related-skill references are bare skill names rather than clearly signaled links, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

62%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 states a clear, specific purpose in third person with an explicit run cadence, and it is well scoped to the Basic Memory niche. Its main weakness is trigger coverage: the natural user phrases ('consolidate', 'review recent work') appear in the body's When to Run section but not in the description itself, and the action list is not comprehensive.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when asked to reflect, consolidate, or review recent work, or after a burst of new notes.'

Surface the natural trigger terms users would say — 'consolidate', 'reflect on recent work', 'review recent notes' — so the description matches how the skill is actually invoked.

Mention one or two more concrete actions (e.g., 'update existing notes in place and record a reflection note') to broaden capability coverage beyond review-and-fold.

DimensionReasoningScore

Specificity

Names the domain ('recent Basic Memory activity') and two concrete actions ('review... activity' and 'fold lasting decisions, lessons, and facts into the notes'), but stops short of listing several distinct actions such as updating existing notes, closing dated fact ranges, or recording a reflection note, so it is not comprehensive.

3 / 5

Completeness

Clearly answers 'what' (review recent activity and fold durable items into the notes they belong in) and gives an explicit 'when' ('Run 1-2x daily, on a heartbeat, or when asked'), but the 'when' side is scheduling-oriented and 'when asked' does not name what the user would ask for, so it is less specific than the anchor-5 example with concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes some relevant keywords ('Basic Memory', 'reflection', 'decisions, lessons, and facts', 'notes') but misses the natural phrases a user would actually say when invoking it, such as 'consolidate', 'review recent work', or 'reflect on this week', which the body's own 'When to Run' section names but the description omits.

3 / 5

Distinctiveness Conflict Risk

'Sleep-time reflection' plus the Basic Memory tool name carves a distinct niche, and the description focuses on reviewing recent activity rather than writing or reorganizing notes, leaving only minor overlap risk with closely related sibling skills like memory-defrag or memory-curate.

4 / 5

Total

14

/

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