OPENCLAWDIRECTORY
📋

Meeting Notes → Action Items

ProductivityIntermediate40 minutes

Transcribe meetings, extract action items, and create follow-up tasks

Prerequisites

  • OpenClaw installed and running
  • Meeting recording capability (Zoom, Google Meet, etc.)
  • Slack workspace for meeting summaries
  • GitHub for task creation (optional)

Required Skills

video-summarizer
openclaw install video-summarizer
slack-digest
openclaw install slack-digest
github-auto-pr
openclaw install github-auto-pr

Installation Steps

1

Install required skills

Install the video summarizer, Slack digest, and GitHub skills.

openclaw install video-summarizer slack-digest github-auto-pr
2

Configure transcription

Set up the transcription service (Deepgram) and specify the recording source and language.

3

Set up task creation

Configure GitHub Issues as the task backend. Action items extracted from meetings will be created as issues assigned to the mentioned person.

4

Add the config snippet

Copy the configuration below and adjust the transcription settings and distribution channels.

Configuration

{
  "meetings": {
    "autoRecord": true,
    "transcription": {
      "service": "deepgram",
      "languages": ["en"]
    },
    "processing": {
      "extractActionItems": true,
      "identifySpeakers": true,
      "generateSummary": true
    },
    "distribution": {
      "slack": "#team-meetings",
      "createTasks": {
        "service": "github-issues",
        "assignees": "mentioned"
      }
    }
  }
}

Add this to your openclaw.json and customize the values for your setup.

SOUL.md

## Meeting Notes Judgment
- Distinguish real action items from casual mentions. "We should probably look into X someday" is not an action item. "Alice will investigate X by Friday" is.
- Attribute action items to the person who volunteered or was assigned, not the person who suggested the idea.
- If someone says "let's take this offline" or "this is off the record," omit that discussion from the summary.
- Summaries should be 5-8 bullet points max, structured as: decisions made, action items, open questions. Nobody reads a 2-page meeting summary.
- When speakers disagree, capture both positions neutrally. Don't editorialize on who was "right."
- If the transcription is unclear about who said something, mark it as [unattributed] rather than guessing wrong.
- For recurring meetings, note what changed since last time — resolved items, new blockers, shifted priorities.

Add this to your SOUL.md to define the agent's behavior for this workflow.

Expected Behavior

After each meeting, OpenClaw transcribes the recording, extracts action items and decisions, generates a summary, posts it to Slack, and creates GitHub issues for each action item assigned to the mentioned person.

Usage Guide

After each meeting ends, the recording is automatically processed. Within minutes, a summary with key decisions and action items appears in #team-meetings on Slack. Each action item is created as a GitHub issue assigned to the responsible person.