菜单
Converts meeting notes, minutes, or call transcripts into decisions, action items with owners and deadlines, open questions, and a sendable recap. Use when the user shares meeting notes or a transcript, or asks for a meeting summary, recap, minutes, follow-ups, or takeaways.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/surfmind-space/awesome-surfmind --skill meeting-follow-up命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Answers a question grounded in the selected text or visible page, researching further when the page falls short, always evidence-backed and never invented. Use when the user highlights a passage or is on a page and asks "what does this mean", "answer this", "where does it say", or any who/what/why/how question about that content.
Turns REST API documentation into a runnable curl, fetch, or code example with required headers, request body, and placeholders for secrets. Use when the user wants to generate a request from API docs, an endpoint, or a Swagger/OpenAPI spec — "give me a curl for this", "show a fetch example", "how do I call this API".
Translates selected text and explains the idioms, cultural nuance, key terms, and phrasing that should not be read literally. Use when the user says "translate this", "in Spanish/French/Japanese/etc.", "what does this mean", "explain this phrase", or wants foreign-language text rendered with the context behind it.
| name | meeting-follow-up |
| description | Converts meeting notes, minutes, or call transcripts into decisions, action items with owners and deadlines, open questions, and a sendable recap. Use when the user shares meeting notes or a transcript, or asks for a meeting summary, recap, minutes, follow-ups, or takeaways. |
| author | surfmind |
| metadata | {"icon":"Calendar","tags":["writing","productivity"]} |
Turn the user's meeting notes or transcript into decisions, action items, open questions, and a sendable recap. Preserve names, numbers, dates, and commitments exactly as stated. Never invent owners or deadlines.
(inferred) rather than asserting it.Return these sections, omitting any that do not apply: Decisions, Action items (one per line as owner — task — due date), Open questions, Suggested follow-up message. Respond in the same language as the user's notes.
Notes:
standup 6/24 — Priya, Marcus, me agreed to ship the export feature behind a flag Marcus takes the API endpoint, due Friday need to decide pricing tier still — ask Dana someone should update the docs
Output:
Decisions
- Ship the export feature behind a feature flag.
Action items
- Marcus — build the export API endpoint — Fri Jun 26
- You (inferred) — update the docs — no due date set
Open questions
- Which pricing tier does export belong to? (ask Dana)
Suggested follow-up message
Hi team — quick recap of today's standup. We're shipping export behind a flag. Marcus owns the API endpoint, targeting Friday. I'll take the docs update. Still open: which pricing tier export lands in — Dana, can you weigh in?
Owner for the docs update isn't explicit in the notes — confirm before sending.