minutes-mcp-recall

1# /minutes-mcp-recall
2 
3Route a meeting-memory question to the smallest useful Minutes MCP tool. This
4skill is tool-name-oriented for MCP hosts such as OpenClaw, Hermes-agent, and
5other MCP clients. Use `minutes-search` instead when the host only has CLI or
6shell access.
7 
8Read [the complete tool map](references/tool-map.md) only when the decision
9table does not cover the request.
10 
11## Decision table
12 
13| User is asking... | Call |
14|---|---|
15| "What did we say about X?" or "Find that meeting about Y." | `search_meetings` |
16| "What is the full transcript of this specific meeting?" | `get_meeting` after finding its id or date with `list_meetings` or `search_meetings` |
17| About what is happening right now, mid-call | `read_live_transcript` with a cursor or time window |
18| "What do I still owe?" or "Who owes me?" | `track_commitments` |
19| "What is my history with this person?" | `get_person_profile` or `relationship_map` |
20| "Have I contradicted myself?" or "Which decisions are stale?" | `consistency_report` |
21| Broad research across many meetings | `research_topic` |
22 
23## Tool-name prefix by host
24 
25- OpenClaw and generic MCP clients use bare tool names such as
26  `search_meetings`.
27- Hermes-agent prefixes each tool with `mcp_minutes_`, so
28  `search_meetings` becomes `mcp_minutes_search_meetings`.
29 
30Apply the same prefix rule to every tool in the decision table and tool map.
31 
32## Anti-patterns
33 
34- Do not call `get_meeting` speculatively to browse. It returns a full
35…