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.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/memory-reflect/SKILL.mdReview what changed recently and fold what matters into the notes that hold durable knowledge. Raw notes (meeting notes, daily logs, captures, transcripts) record what happened; reflection decides what of it should still be known next month, and puts it where someone will look for it.
Inspired by sleep-time compute: memory forms best between working sessions, not during them.
If the project is unknown, discover it with bm_project_list().
Pass a nonempty project on every note, folder, context and schema call, even
with one project or a qualified memory:// URL. Use the chosen project's name,
workspace/project, or external ID; <project> below is a placeholder for it.
Recent activity also requires project. Search accepts project for one
project, projects for selected projects, or all_projects=True explicitly.
Discovery and bundled manuals need no project. Keep the same scope when following
returned paths, paginating, or recovering from a refusal.
# The last reflection is the checkpoint. Titles carry date and time, so the
# newest sorts first.
bm_list(path="reflections", sort="title_desc", page_size=1, project="<project>")
# Everything changed since that date (json gives one row per note). With no
# reflection yet, use since="7d".
bm_recent(since="2026-10-13", items=["note"], output_format="json", page_size=50, project="<project>")
# Ask for page=2, 3, ... until has_more is false.
# Read each changed note in full before judging it
bm_read(identifier="meetings/2026-10-14-launch-sync", project="<project>")Timeframes count whole days, so the window can overlap the last reflection.
Skip notes it lists as reviewed, and notes you wrote in an earlier
reflection, unless someone edited them since.
bm_recent(project="<project>") looks back at most a year. If the last reflection is older
than that, use since="365d" and record in this reflection that changes
before that window were not reviewed.
For each item, ask:
| Kind | Keep? |
|---|---|
| A decision and its reason | Keep |
| A lesson or mistake to avoid | Keep |
| A preference or way of working | Keep |
| Who owns or knows what | Keep |
| A commitment with an owner and date | Keep, as a task or on the project note |
| A change to something already recorded | Keep, and date the change in the old note |
| Routine or transient detail (a check ran, a file moved) | Skip |
| Already recorded in a durable note | Skip |
Find the durable note for each item before writing anything:
bm_search(query="launch checklist owner", project="<project>")
bm_context(identifier="memory://projects/launch", project="<project>")Say when it holds. A fact with a date gets a qualifier (see
memory-notes): @effective: for a decision or rule, @occurred: for an
event, @due: for a commitment. Use the date the source gives, not today's.
- [decision] @effective:2026-10-14 Launch moves to Thursday
- [deadline] @due:2026-10-20 Draft ready for reviewA fact changed: close the old fact's range rather than deleting it, so both stay searchable by date. Do this only when the source says what changed and when; if it only disagrees, record both with "(needs confirmation)".
- [decision] @effective[2026-09-01,2026-10-14) Launch on Friday
- [decision] @effective:2026-10-14 Launch on ThursdayThe topic has a note: update it in place. Read it as JSON and pass its checksum to the edit, so the edit applies only to the revision you read.
note = bm_read(identifier="Launch Plan", output_format="json", project="<project>")
bm_edit(
identifier="Launch Plan",
command="replace_section",
section="## Owners",
content="- [owner] Maya owns the launch checklist",
expected_checksum=note["checksum"],
project="<project>",
)If the edit reports a checksum conflict, someone changed the note after you read it: read it again and decide again from the new text.
The topic has no note: create one with bm_write, following
memory-notes: a clear title, observations with categories, and relations.
Link back: every consolidated fact names its source, e.g.
- derived_from [[2026-10-14 Launch Sync]], so a reader can check it.
Write one note per reflection in reflections/, titled with the date and time
so two runs on one day get separate notes and the newest sorts first. The next
reflection starts from it:
---
title: Reflection 2026-10-14 0830
type: reflection
---
# Reflection 2026-10-14 0830
## Observations
- [reviewed] 6 notes changed since the last reflection
- [updated] Launch Plan: owner of the checklist is now Maya
- [created] Release Checklist Owners
- [unsure] Whether the dashboard idea was agreed or only suggested (needs confirmation)
## Relations
- reviewed [[2026-10-14 Launch Sync]]
- updated [[Launch Plan]]expected_checksum so you change only that revision.basicmachines-co/basic-memory
4519c23
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.