- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-copilot -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-copilot -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-copilot -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-copilot -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/silverstein/minutes/tree/HEAD/.agents/skills/minutes/minutes-copilotFrom the publisher
Use the real Minutes copilot runtime to start or control Coach. Do not build a transcript reader, event poller, prompt loop, or shell tailer in this skill.
If the user explicitly asks you or the current terminal agent to watch, advise, or strategize, use /minutes-live-sidekick instead. If the user says only "coach me live" or otherwise leaves the surface ambiguous, ask exactly: "Do you want me in this terminal to be your sidekick, or should I open the Minutes Coach HUD?" Do not start Coach while clarifying.
sales, discovery, interview, negotiation, difficult-conversation, decision, or generic. Default to generic.tui surface. Never invent an MCP tool name.minutes copilot start --goal '<meeting goal>' --surface tui --mode generic
The tui surface is the Coach HUD. Keep the command attached as the live session. Add --live only when the user explicitly asks Coach to own a standalone capture; normally Coach attaches to the existing Minutes capture stream.
Use the matching real MCP control when present; otherwise run exactly one of:
minutes copilot status
minutes copilot pause
minutes copilot resume
minutes copilot stop
Do not start a second session when minutes copilot status reports one active. Pausing or stopping Coach must not stop recording.
After a successful start, report the goal and mode in one line: Coach is listening — goal: <goal> · mode: <mode>. For status or control actions, relay the command result concisely. If the provider is unavailable, say that Coach degraded or did not start and make clear that recording remains unaffected.
Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach
---name: minutes-copilotdescription: Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only…---# .agents/skills/minutes/minutes-copilot/SKILL.mdOverview
Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.
FAQ
Download .agents/skills/minutes/minutes-copilot/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/silverstein/minutes.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.