memory-recall

name	memory-recall
description	Auto-activate on any question about past work, decisions, commands, facts, or current status ("what did we do this morning/yesterday/today", "how\
s everything looking", "what\'s in flight", "remember when", "have we seen this error before", "what is the IP of X"). Encodes R…	status/workboard protocol, time-bounded browse first, multi-angle search + trigram fallback.'
tags	["rivetos","memory","recall","discipline","rivet-memory","status"]
version	0.2.1

RivetOS Memory Recall Discipline (Kimi Code CLI)

You have access to a shared, persistent memory store used by every Rivet agent (rivet-claude, rivet-hermes, rivet-grok, rivet-kimi, etc.) via the RivetOS MCP server.

The tools are excellent. The usual failure mode is poor discipline — using semantic search when a chronological browse of a known time window is the correct reflex.

This skill exists so you reach for the right tool on the first try.

The Core Rules (Best of Hermes + Claude + Grok)

0. Status / "how's things" / "what's in flight"? → Workboard first

Prompts like "how's everything looking", "status", "catch me up" mean current work across agents, not memory_stats or box health.

1. memory_browse(window="last_24h") — read user/assistant closers across agents.
2. Treat workspace memory/*.md notes as hints to verify, never as current state.
3. Host/memory_stats only as a secondary note when relevant.

1. Time-bounded question? → memory_browse with window= FIRST

Any prompt that pins a timeframe ("this morning", "yesterday", "today", "earlier", "last week", "the standup", "what we did on Tuesday") means the user already knows when. They need exhaustive results in order, not relevance-ranked hits.

Use the enhanced window= parameter whenever available:

• window="this_morning" | "yesterday" | "today" | "this_week" | "last_24h" | "last_7d" | "last_14d" (prefer rolling last_7d over calendar this_week early in the week)

This is the preferred path because it correctly handles local timezone boundaries without you doing math.

Fallback: Explicit since / before as full UTC ISO timestamps (never bare dates).

Important: After a browse that hits the limit, flip order="asc" or increase limit (max usually 200) instead of assuming you have everything.

Default browse excludes role=tool. Pass include_tools=true only when debugging capture, harness wiring, or tool failures.

2. Topic / lookup question (no clear timeframe)? → Multi-angle search, minimum 3 queries

One embedding call is fragile. Run from different semantic vectors:

• Service / role: "frigate NVR", "openwrt router"
• Host / nickname: "minipc", "example-host"
• Network: use documentation examples only (e.g. RFC5737 192.0.2.0/24 in public docs)
• Exact tokens: IPs, MACs, error strings, port numbers → use mode="trigram"

FTS power move (when supported):

• memory_search(query="frigate OR minipc OR \"error 1234\"", mode="fts") — real OR, phrases, exclusions.

3. Semantic/FTS returns thin? Immediately retry with mode="trigram"

The moment you get 0–2 results on something that should exist, re-issue the same queries with trigram mode. Literal token matches (hostnames, error messages, config values) are often indexed under different surrounding text.

4. "No results" is a signal to try harder — never the final answer

Treat empty results + any user pushback as a cue to change strategy:

• Switch to browse with a wider window
• Add more angles or trigram
• Check cross-agent history (filter by agent only when you specifically want to exclude other Rivet faces)

Only after exhausting the memory tools should you consider external actions.

Decision Flow

User asks about past / status / "remember" / facts
          │
          ▼
Status / how's things / in flight?
   YES → workboard browse (rule 0)
   NO
          │
          ▼
Mentions clear timeframe?
   YES                     NO
    │                       │
    ▼                       ▼
memory_browse          3× memory_search
(window= preferred)    (different angles)
    │                       │
    ▼                       ▼
Still thin?             Thin results?
    │                       │
    ▼                       ▼
Widen window           Retry with mode=trigram
or raise limit             + FTS OR syntax
    └───────────┬───────────┘
                ▼
User unhappy? → Change strategy again.
Do not give up and probe externally yet.

Kimi Code Specific Tool Usage

1. Discover the exact MCP tool names for the RivetOS server. Depending on how kimi-code surfaces MCP tools, they may appear as memory_search / memory_browse / memory_stats, or as qualified names such as rivetos__memory_search. Check the available tools list before calling.
2. Call the tools with the documented parameters (window=, mode=, agent=, etc.).
3. For time-bounded questions, strongly prefer the window= parameter on browse when the server supports it.

Cross-Agent Reality

Memory hits may be tagged with agent = "rivet-claude", "rivet-hermes", "rivet-grok", "rivet-kimi", etc. This is a feature. A question like "what did we decide about X" should surface the best answer regardless of which Rivet face originally did the work.

Only filter by agent when the user explicitly wants the history from one specific lineage.

Why This Exists (Case Study)

See the 2026-05-23 WAP-DHCP incident (documented in the Claude and Hermes versions of this skill). Multiple rounds of memory_search on topic keywords returned nothing. Only a forced memory_browse over the known morning window surfaced the full context.

This skill prevents repeating that expensive mistake.

Related Patterns

• Write synonym-bridging memory entries when you discover facts through probing or user correction.
• Use memory_stats to understand coverage and health.
• Pre-compaction messages are captured when hooks are enabled — they are high-value for long sessions.