跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

meeting-prep

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.

运维与云558nanomuse/skills/builtin/meeting-prep/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/nano-muse/nanomuse/meeting-prep/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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)

  1. When and where: from the event, time, place or link, duration.
  2. Who: one line per person, name, role, company, the relationship in a few words.
  3. Where things stand: the last exchange, the open questions, promises made (by whom, when).
  4. What you want from it: two or three outcomes, drawn from goals and the last exchange; phrase them as sentences the user could say.
  5. To bring / to have read: files, numbers, decisions.
  6. 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.

相似的 Skill

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

运维与云

shipping-and-launch
addyosmani/agent-skills104k

shipping-and-launch

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

运维与云

observability-and-instrumentation
addyosmani/agent-skills104k

observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

运维与云

internal-comms
ComposioHQ/awesome-claude-skills77k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

运维与云

vercel-react-best-practices
CherryHQ/cherry-studio52k

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

运维与云

acceptance-orchestrator
sickn33/agentic-awesome-skills47k

acceptance-orchestrator

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

运维与云