CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-reflect

Sleep-time memory reflection: review recent conversations and daily notes, extract insights, and consolidate into long-term memory. Use when triggered by cron, heartbeat, or explicit request to reflect on recent activity. Runs as background processing to improve memory quality over time.

66

Quality

79%

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-reflect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-structured instruction skill: concrete tool examples, an explicit evaluation rubric, and useful guardrail guidelines with no padding or restatement of known concepts. The main gaps are a trimmable motivation line and the absence of a validation step after batch memory updates.

Suggestions

Drop or compress the 'Inspired by sleep-time compute' motivation line — it explains a concept rather than instructing, freeing tokens for guidance.

Add an explicit validation step after Step 3, e.g. re-read MEMORY.md after edits to confirm no duplicates or broken sections were introduced, before logging the reflection.

Tighten actionability by specifying the note types and timeframe parameters for the gather step (e.g. which note_types recent_activity should filter for) so the tool calls are closer to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — the keep/skip checklist and guidelines are all signal. One flavor line ('Inspired by sleep-time compute — the idea that memory formation happens best between active sessions') is motivation rather than instruction and could be trimmed, so it sits at 4 rather than 5.

4 / 5

Actionability

Concrete tool-call examples with signatures, a six-item keep/skip decision checklist, and a copy-ready log template make the guidance mostly executable. The tool calls use justified dynamic placeholders (memory/<YYYY-MM-DD>) and leave a few parameters implicit, which keeps it below 5.

4 / 5

Workflow Clarity

Four clearly sequenced steps (gather → evaluate → update → log) with partial checkpoints ('Flag uncertainty', 'Merge, don't append', the reflection log). Because the batch MEMORY.md update includes removals and restructuring without an explicit post-edit validation pass, it stays at 4 rather than 5; guardrails like 'Don't delete daily notes' keep it well above 3.

4 / 5

Progressive Disclosure

Well-organized sections with everything appropriately placed in a single file and no content that clearly belongs in a separate reference. The under-50-line simple-skill exception (the body is ~68 lines) doesn't strictly apply, so it scores 4 rather than 5; it is clearly not 3 since nothing externalizable is inlined.

4 / 5

Total

16

/

20

Passed

Description

83%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: third-person voice, concrete capability list, and an explicit 'Use when...' clause with multiple natural trigger terms. Only slightly short of top marks on keyword comprehensiveness and distinctiveness.

DimensionReasoningScore

Specificity

Lists several concrete actions ('review recent conversations and daily notes, extract insights, and consolidate into long-term memory') with named artifacts. Falls short of 5's comprehensive coverage since it doesn't enumerate the full action set, but exceeds 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both what ('review recent conversations and daily notes, extract insights, and consolidate into long-term memory') and when ('Use when triggered by cron, heartbeat, or explicit request to reflect on recent activity') with concrete trigger phrases — a direct match for the 5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'cron', 'heartbeat', 'explicit request to reflect', 'reflect on recent activity' — phrases a user or scheduler would actually produce. A few natural variations ('consolidate memory', 'review notes') are missing, so not 5.

4 / 5

Distinctiveness Conflict Risk

'Sleep-time memory reflection' names a clear niche with distinct background-processing triggers, giving minimal conflict risk. Minor overlap remains with generic 'review my notes' requests, keeping it below the 5 anchor's 'clear niche with distinct triggers'.

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