2026-06-22 09:27:36 -05:00
|
|
|
|
---
|
|
|
|
|
|
description: Reflect on this session — extract durable memories and propose them for one-tap capture
|
|
|
|
|
|
argument-hint: "[optional focus, e.g. 'just decisions']"
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
Use the **echo-memory** skill to run **session reflection** (H5). Scan this conversation for
|
|
|
|
|
|
things worth remembering across sessions, then propose them — don't write blindly.
|
|
|
|
|
|
|
|
|
|
|
|
1. **Extract** durable items from the conversation: new facts, preferences, decisions,
|
2026-06-23 22:17:39 -05:00
|
|
|
|
commitments, people/companies/projects introduced, and anything the operator said to remember.
|
2026-06-22 09:27:36 -05:00
|
|
|
|
Skip the ephemeral. Anchor relative dates on the conversation's `currentDate`.
|
|
|
|
|
|
2. **Emit a JSON array** of proposals (one per item), each:
|
|
|
|
|
|
`{"title","kind","body","aliases","sources","confidence"}` — `kind` ∈
|
|
|
|
|
|
`person, company, concept, reference, meeting, project, area, semantic, episodic,
|
|
|
|
|
|
working, skill, decision`; set `"inbox": true` when the home is genuinely unknown;
|
|
|
|
|
|
`confidence` 0–1 (items below 0.6 are dropped — send those to the inbox instead).
|
|
|
|
|
|
Write the array to a file with the Write tool (cross-platform; no heredoc).
|
2026-06-23 22:17:39 -05:00
|
|
|
|
3. **Preview, then apply.** Dry-run first (writes nothing) and show the operator the plan; only
|
|
|
|
|
|
apply after they confirm.
|
2026-06-22 09:27:36 -05:00
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py" # python3 (Windows: python / py -3)
|
2026-06-26 20:05:47 -05:00
|
|
|
|
[ -f "$ECHO" ] || ECHO=$(ls /sessions/*/mnt/.remote-plugins/*/skills/echo-memory/scripts/echo.py 2>/dev/null | head -1) # CoWork sandbox fallback
|
2026-06-22 09:27:36 -05:00
|
|
|
|
python3 "$ECHO" reflect proposals.json # dry-run: validate + classify + preview
|
|
|
|
|
|
python3 "$ECHO" reflect proposals.json --apply # write — routes each via capture (indexed, linked, logged)
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
`reflect` dedups every proposal against the entity index (so it shows create-vs-update),
|
|
|
|
|
|
skips below-confidence items, and routes `inbox` proposals to the capture inbox. Each
|
|
|
|
|
|
applied item goes through the normal `capture` path — canonical frontmatter, auto-linking,
|
|
|
|
|
|
and the recall index — and the writes are lock-guarded. $ARGUMENTS
|
