meeting-notes
GitHub将会议原始记录或转录稿转化为结构化摘要,提取关键决策、明确行动项及待办事项,确保信息清晰可执行。
Trigger Scenarios
Install
npx skills add holaboss-ai/holaOS --skill meeting-notes -g -y
SKILL.md
Frontmatter
{
"name": "meeting-notes",
"description": "Turn raw notes or a transcript into a clean summary with decisions and action items."
}
Meeting Notes
Turn the mess of a meeting — half-sentences, tangents, crosstalk — into a record someone who wasn't there can act on. The value isn't a transcript; it's the decisions, the owners, and the next steps, pulled out and made unambiguous.
When to use this skill
Use Meeting Notes on raw notes, a rough transcript, or a recording summary to produce a structured recap: what was decided, who owns what, and what's still open. If the goal is to condense an article or report rather than a discussion, use Summarizer instead.
What a good recap captures
- Decisions — what the group actually agreed, stated plainly. Distinguish a decision from a suggestion that went nowhere.
- Action items — each with an owner and, where stated, a due date. An action with no owner is a wish; assign it or flag it as unassigned.
- Open questions — things raised but not resolved, so they don't quietly vanish.
- Context — just enough of the "why" that a decision doesn't read as arbitrary later.
Principles
- Signal over transcript. Don't replay the conversation — extract what matters and drop the rest.
- Attribute carefully. Only assign an owner or a decision if the input actually supports it. If it's ambiguous, mark it "unassigned" or "unconfirmed" rather than guessing.
- Never invent. If a date, owner, or decision wasn't stated, say so. Fabricated specifics are worse than an honest gap.
- Neutral voice. Record what was said, not your opinion of it.
How to work
- Read the full input and separate discussion from outcomes.
- Pull out decisions, then action items (owner + due date where given), then open questions.
- Write a two-to-three sentence summary at the top so a skimmer gets the gist.
- Re-check every owner, date, and decision against the source; flag anything you had to infer.
Output format
Lead with a short Summary, then Decisions, Action items (as a checklist with owners), and Open questions. Omit any section that genuinely has nothing in it rather than padding it.
Version History
- f6013b5 Current 2026-08-19 23:16


