How do I install the Minutes MCP Recall skill?

Run npx skillmds@latest add silverstein/minutes-mcp-recall in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Minutes MCP Recall skill do?

Route meeting-recall questions to the right Minutes MCP tool. It is listed under AI & ML on SkillMD.

Is Minutes MCP Recall safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Minutes MCP Recall?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Minutes MCP Recall free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Minutes MCP Recall?

silverstein (@silverstein) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Minutes MCP Recall by silverstein — Agent Skill

Name: Minutes MCP Recall
Rating: 4.666666666666667 (3 reviews)
Author: silverstein

File contents

Skill Path

Before running helper scripts or opening bundled references, set:

export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-mcp-recall"

/minutes-mcp-recall

Route a meeting-memory question to the smallest useful Minutes MCP tool. This skill is tool-name-oriented for MCP hosts such as OpenClaw, Hermes-agent, and other MCP clients. Use minutes-search instead when the host only has CLI or shell access.

Read the complete tool map only when the decision table does not cover the request.

Decision table

User is asking...	Call
"What did we say about X?" or "Find that meeting about Y."	`search_meetings`
"What is the full transcript of this specific meeting?"	`get_meeting` after finding its id or date with `list_meetings` or `search_meetings`
About what is happening right now, mid-call	`read_live_transcript` with a cursor or time window
"What do I still owe?" or "Who owes me?"	`track_commitments`
"What is my history with this person?"	`get_person_profile` or `relationship_map`
"Have I contradicted myself?" or "Which decisions are stale?"	`consistency_report`
Broad research across many meetings	`research_topic`

Tool-name prefix by host

OpenClaw and generic MCP clients use bare tool names such as search_meetings.
Hermes-agent prefixes each tool with mcp_minutes_, so search_meetings becomes mcp_minutes_search_meetings.

Apply the same prefix rule to every tool in the decision table and tool map.

Anti-patterns

Do not call get_meeting speculatively to browse. It returns a full transcript. Use search_meetings or list_meetings first to find the right id or date and preserve context budget.
Do not call read_live_transcript without a cursor after one is available. Replaying the whole transcript wastes tokens and duplicates content already in context.
Do not use capture, dictation, processing, annotation, or speaker-mutation tools for a recall question.

---name: minutes-mcp-recalldescription: Route meeting-recall questions to the right Minutes MCP tool.--- ## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-mcp-recall" ``` # /minutes-mcp-recall Route a meeting-memory question to the smallest useful Minutes MCP tool. This skill is tool-name-oriented for MCP hosts such as OpenClaw, Hermes-agent, and other MCP clients. Use `minutes-search` instead when the host only has CLI or shell access. Read [the complete tool map](references/tool-map.md) only when the decision table does not cover the request. ## Decision table | User is asking... | Call | |---|---| | "What did we say about X?" or "Find that meeting about Y." | `search_meetings` | | "What is the full transcript of this specific meeting?" | `get_meeting` after finding its id or date with `list_meetings` or `search_meetings` | | About what is happening right now, mid-call | `read_live_transcript` with a cursor or time window | | "What do I still owe?" or "Who owes me?" | `track_commitments` | | "What is my history with this person?" | `get_person_profile` or `relationship_map` | | "Have I contradicted myself?" or "Which decisions are stale?" | `consistency_report` | | Broad research across many meetings | `research_topic` | ## Tool-name prefix by host - OpenClaw and generic MCP clients use bare tool names such as `search_meetings`. - Hermes-agent prefixes each tool with `mcp_minutes_`, so `search_meetings` becomes `mcp_minutes_search_meetings`. Apply the same prefix rule to every tool in the decision table and tool map. ## Anti-patterns - Do not call `get_meeting` speculatively to browse. It returns a full transcript. Use `search_meetings` or `list_meetings` first to find the right id or date and preserve context budget. - Do not call `read_live_transcript` without a cursor after one is available. Replaying the whole transcript wastes tokens and duplicates content already in context. - Do not use capture, dictation, processing, annotation, or speaker-mutation tools for a recall question.

Frequently asked questions

Minutes MCP Recall