- 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 nano-muse/nanoMuse --skill meeting-prep -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill meeting-prep -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill meeting-prep -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nano-muse/nanoMuse --skill meeting-prep -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/nano-muse/nanoMuse/tree/HEAD/nanomuse/skills/builtin/meeting-prepFrom the publisher
A brief at meetings/YYYY-MM-DD-<slug>.md in the workspace, and its gist in chat. Works with any of the connectors; the more are there, the fuller the brief.
calendar action=search for it; otherwise calendar action=agenda for today and tomorrow and take the next one that has other people in it. If nothing fits, ask with one ask_user: which meeting, and with whom.contacts action=search by name or address: company, role, how the user knows them. Unknown people stay a bare name; do not look them up on the web unless the user asks.read_emails search=<their name or address>, the last few weeks. You want the last thing said in each direction, open questions, and anything the user promised.recall each name and the company: past notes, preferences, what went wrong last time.files action=search for the company, the project or the meeting's title; list the two or three that matter with a one-line note.goals that mention the people or the topic: the current step is what the user probably wants out of the meeting.A page, not a report. Nothing the sources did not say; a section with nothing in it is left out.
Chat: two or three lines (who, what it is about, the one thing to remember) and the brief's name. After the meeting, if the user tells you how it went, remember the decisions and goals the follow-ups; offer that in one sentence, and stop.
Prepare for a meeting (who is in it, what was last said with them, what the user owes them and wants from them) as a one-page brief. Use when the user asks to prepare for or get ready for a meeting, a
---name: meeting-prepdescription: Prepare for a meeting (who is in it, what was last said with them, what the user owes them and wants from…---# nanomuse/skills/builtin/meeting-prep/SKILL.mdOverview
Prepare for a meeting (who is in it, what was last said with them, what the user owes them and wants from them) as a one-page brief. Use when the user asks to prepare for or get ready for a meeting, a call or a visit; a trigger can run it before every meeting with a client.
FAQ
Download nanomuse/skills/builtin/meeting-prep/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/nano-muse/nanoMuse.
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.