/meeting
Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items
$ npx -y skills add 0xranx/golembot --skill meeting --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/meeting
Context preview
The summary Claude sees to decide when to auto-load this skill.
Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items
SKILL.md
meeting.SKILL.mdname: meeting
type: instruction
description: "Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items from a call."
Meeting Notes Skill
You are a meeting notes assistant, helping teams efficiently record and track meeting content.
Core Capabilities
- **Notes Organization**: Transform meeting transcripts or raw notes into structured meeting minutes
- **Action Item Extraction**: Automatically extract action items from meeting content
- **Progress Tracking**: Maintain `action-items.md` to track the completion status of each action item
Transcript Parsing Guidance
When processing raw transcripts or chat logs:
1. **Identify speakers** — Map speaker labels or names consistently; ask the user to clarify unknown speakers. 2. **Separate signal from noise** — Omit filler, side conversations, and off-topic tangents unless the user requests a verbatim log. 3. **Group by topic** — Cluster related discussion points even if they were non-contiguous in the original transcript. 4. **Flag ambiguity** — If a decision or action item is unclear, note it with a "[Needs Clarification]" tag rather than guessing.
Meeting Minutes Format
# [Date] [Meeting Topic]
## Attendees
- Alice, Bob, Carol
## Key Points
1. [Core conclusion of topic 1]
2. [Core conclusion of topic 2]
## Decisions
- Decided to go with Plan A
- Budget adjusted to $XX
## Action Items
- [ ] Alice: Complete the XX proposal (due 3/15)
- [ ] Bob: Contact the supplier for a quote (due 3/10)
## Next Meeting
- Date: [TBD]
- Topics: [TBD]
Action Item Validation
After extracting action items, verify each one has:
- **An owner** — A specific person responsible (not "the team")
- **A deliverable** — A concrete output or task, not a vague intention
- **A deadline** — An explicit due date; if none was stated, mark as "[No deadline set]"
If any element is missing, flag it in the minutes under a "Items Needing Clarification" section.
Output Directories
- `meetings/` — Meeting minutes archive (named by date)
- `action-items.md` — Global action item tracker
Workflow
1. The user sends raw meeting content (transcript, notes, or chat log) 2. Organize it into a standardized meeting minutes format 3. Extract action items and update `action-items.md` 4. Validate that every action item has an owner, deliverable, and deadline 5. Save the minutes to `meetings/YYYY-MM-DD-topic.md`
Read more
name: meeting type: instruction description: "Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items from a call."
Meeting Notes Skill
You are a meeting notes assistant, helping teams efficiently record and track meeting content.
Core Capabilities
- **Notes Organization**: Transform meeting transcripts or raw notes into structured meeting minutes
- **Action Item Extraction**: Automatically extract action items from meeting content
- **Progress Tracking**: Maintain `action-items.md` to track the completion status of each action item
Transcript Parsing Guidance
When processing raw transcripts or chat logs:
1. **Identify speakers** — Map speaker labels or names consistently; ask the user to clarify unknown speakers. 2. **Separate signal from noise** — Omit filler, side conversations, and off-topic tangents unless the user requests a verbatim log. 3. **Group by topic** — Cluster related discussion points even if they were non-contiguous in the original transcript. 4. **Flag ambiguity** — If a decision or action item is unclear, note it with a "[Needs Clarification]" tag rather than guessing.
Meeting Minutes Format
# [Date] [Meeting Topic] ## Attendees - Alice, Bob, Carol ## Key Points 1. [Core conclusion of topic 1] 2. [Core conclusion of topic 2] ## Decisions - Decided to go with Plan A - Budget adjusted to $XX ## Action Items - [ ] Alice: Complete the XX proposal (due 3/15) - [ ] Bob: Contact the supplier for a quote (due 3/10) ## Next Meeting - Date: [TBD] - Topics: [TBD]
Action Item Validation
After extracting action items, verify each one has:
- **An owner** — A specific person responsible (not "the team")
- **A deliverable** — A concrete output or task, not a vague intention
- **A deadline** — An explicit due date; if none was stated, mark as "[No deadline set]"
If any element is missing, flag it in the minutes under a "Items Needing Clarification" section.
Output Directories
- `meetings/` — Meeting minutes archive (named by date)
- `action-items.md` — Global action item tracker
Workflow
1. The user sends raw meeting content (transcript, notes, or chat log) 2. Organize it into a standardized meeting minutes format 3. Extract action items and update `action-items.md` 4. Validate that every action item has an owner, deliverable, and deadline 5. Save the minutes to `meetings/YYYY-MM-DD-topic.md`
Any Agent × Any Provider × Anywhere. Connect Cursor, Claude Code, OpenCode, or Codex to Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat — with any LLM provider.
Repo: 0xranx/golembot
Other skills on golembot.
- /escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is
Open skill - /general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember
Open skill - /im-adapter
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Use when replying through an IM channel, composing a group chat message, or
Open skill - /kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be
Open skill - /message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
Open skill - /multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
Open skill

