mcpbeat

Minutes Ideas

silverstein/minutes-.opencode-minutes-ideas

Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.

376 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1405
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/silverstein/minutes --skill minutes-ideas

The instruction itself

3 sections, as written by the author

/minutes-ideas — Recent Voice Memos & Ideas

Surface voice memos and ideas captured from any device in the last 14 days.

This is the recall layer for the cross-device ghost context pipeline.

How to run

  • Search for recent voice memos using the minutes CLI:
minutes list --content-type memo --limit 20
  • Require exit status 0 and use the JSON written to stdout. If the CLI is

unavailable or fails, report the memo source unavailable; never scan the

memo directory directly.

  • Present the memos as a clean list:
  • Date, title, duration, device (if from iPhone)
  • Ask: "Want to dig into any of these?"
  • If the user picks one, run minutes get "<exact path>" --json, require exit

status 0, and present only the returned transcript/summary. Never reopen the

list path through the host filesystem.

Ghost Context

These memos were captured on the user's phone (or Mac) and automatically

transcribed by the Minutes watcher. They may contain ideas, thoughts,

observations, or reminders that the user recorded while away from their desk.

When the user asks "what was that idea I had while walking?" — search these

memos first, then broaden to full meeting search if needed.

How to use it

Copy the folder

Take silverstein/minutes-.opencode-minutes-ideas from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.