Agent Skills › nano-muse/nanoMuse › meeting-prep

meeting-prep

GitHub

根据日历、联系人邮件及工作区文件，自动生成会议准备简报。涵盖参会人员背景、历史沟通状态、待办事项及关键注意事项，帮助用户高效准备会议。

nanomuse/skills/builtin/meeting-prep/SKILL.md nano-muse/nanoMuse

Trigger Scenarios

用户要求准备会议或通话会前自动触发以获取上下文

Install

npx skills add nano-muse/nanoMuse --skill meeting-prep -g -y

More Options

Non-standard path

npx skills add https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/meeting-prep -g -y

Use without installing

npx skills use nano-muse/nanoMuse@meeting-prep

指定 Agent (Claude Code)

npx skills add nano-muse/nanoMuse --skill meeting-prep -a claude-code -g -y

安装 repo 全部 skill

npx skills add nano-muse/nanoMuse --all -g -y

预览 repo 内 skill

npx skills add nano-muse/nanoMuse --list

SKILL.md

Frontmatter

{
    "name": "meeting-prep",
    "channel": "mixed",
    "metadata": {
        "author": "nanoMuse",
        "version": "1"
    },
    "description": "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."
}

Meeting prep

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.

Find the meeting

If the user named it, 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.
A trigger (kind=event) gives you the event as context: use it as is, do not search again.

The people

Each attendee: 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.
With the mail connector: 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.

The matter

Related files in the workspace: 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.
Active goals that mention the people or the topic: the current step is what the user probably wants out of the meeting.

The brief (Markdown)

When and where: from the event, time, place or link, duration.
Who: one line per person, name, role, company, the relationship in a few words.
Where things stand: the last exchange, the open questions, promises made (by whom, when).
What you want from it: two or three outcomes, drawn from goals and the last exchange; phrase them as sentences the user could say.
To bring / to have read: files, numbers, decisions.
Watch out: anything from memory or mail that would embarrass (a missed deadline, a name they get wrong).

A page, not a report. Nothing the sources did not say; a section with nothing in it is left out.

Finish

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.