‹ 首页

meeting-notes-to-tasks

@developersglobal · 收录于 1 周前

Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.

适合你,如果每次会后都要花时间整理待办事项

/ 下载安装
meeting-notes-to-tasks.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add developersglobal/ai-agent-skills/meeting-notes-to-tasks
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- developersglobal/ai-agent-skills/meeting-notes-to-tasks
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify developersglobal/ai-agent-skills/meeting-notes-to-tasks
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
64GitHub stars
~550上下文体积 · 单文件
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · f47f948
Overview

Meetings produce decisions and commitments. Without structure, these dissolve into vague memory. This skill transforms raw meeting notes into a concrete, actionable task list.

When to Use
  • After any meeting with decisions or commitments
  • When processing meeting transcripts or notes
  • When preparing follow-up communication
Process
Step 1: Extract Decisions
  1. Read all notes.
  2. List every decision made: Decision: [what was decided]
  3. Distinguish decisions from discussions (decisions = agreed outcomes, not explorations).

Deliver: A numbered list of decisions made.

Step 2: Extract Action Items
  1. For each commitment made, write: ``` Action: [specific deliverable] Owner: [person's name] Due: [specific date, not "soon" or "next week"] Context: [1-sentence background] ```
  2. If an owner is not named: flag it — unowned actions are undone actions.
  3. If a due date is not named: flag it — undated actions are undone actions.

Deliver: Structured action items with owner and due date for every commitment.

Step 3: Identify Blockers and Dependencies
  1. What action items are blocked by other action items?
  2. What external dependencies exist (waiting on third party, requires approval, etc.)?
  3. What open questions remain unresolved?

Deliver: Blocker list and open questions with owners.

Step 4: Draft Follow-Up Summary
  1. Compose a concise follow-up message:
  2. Decisions (bullet list)
  3. Action items (table: action | owner | due date)
  4. Open questions (bullet list with owner)
  5. Next meeting date (if applicable)

Deliver: Ready-to-send follow-up email/Slack message.

Common Rationalizations (and Rebuttals)

| Excuse | Rebuttal | |--------|----------| | "Everyone knows what they need to do" | They don't. Write it down. | | "The notes are good enough" | Notes describe what was said. Action items describe what will be done. | | "We'll follow up informally" | Informal follow-up means things fall through the cracks. |

Verification
  • [ ] Every decision captured
  • [ ] Every action item has: owner, due date, specific deliverable
  • [ ] Unowned/undated items flagged
  • [ ] Blockers and open questions identified
  • [ ] Follow-up summary drafted and ready to send
References
  • [goal-driven-execution skill](../goal-driven-execution/SKILL.md)
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。