---
name: meeting-intel
title: Meeting Intelligence Analyzer
description: "Comprehensive AI meeting intelligence system. Goes far beyond summaries — produces strategic intelligence: prioritized action items, communication playbooks, team dynamics analysis, topic deep-dives, risk/opportunity radar, and political landscape awareness. Accepts any transcript format. Scales from standup briefs to full strategy reports."
category: workflow
tags:
  - meetings
  - analysis
  - strategy
  - action-items
  - communication
  - team-dynamics
requires:
  - Claude
source: https://madejski.ai/skilloteka/meeting-intel
locale: en
license: MIT
---

# Meeting Intelligence Analyzer

## What This Skill Does

This is not a meeting summarizer. It's a strategic intelligence extraction system that treats every meeting as a source of actionable knowledge. The output gives you everything you need to act decisively after a meeting — without re-reading the transcript.

The system produces a multi-layered analysis document calibrated to the meeting's complexity: a 15-minute standup gets a focused 1-page brief; a 2-hour strategy session gets a full intelligence report.

## Input Handling

The skill accepts transcripts in any format:

- **Fireflies.ai exports** — JSON, markdown, or plain text
- **Otter.ai notes** — any export format
- **Teams/Zoom/Google Meet** transcripts or auto-generated summaries
- **Pasted raw text** — speaker-labeled or unlabeled conversation
- **Uploaded files** — .txt, .md, .json, .docx, .pdf containing meeting content
- **Conversation from memory** — you describe what happened; skill works with what's available

### Identifying the Principal

The analysis is always written from one person's perspective — the Principal. If the user doesn't specify, ask who the Principal is. The Principal's name may appear in various forms in the transcript.

## Analysis Framework

The framework has 10 sections — not all are needed for every meeting:

### Always include (every meeting):
1. **Meeting Metadata** — date, participants, duration, type
2. **Executive Summary** — 3-5 sentences, what happened and why it matters
3. **Decisions and Commitments** — what was decided, by whom, with what authority
4. **Action Items Matrix** — every task with owner, deadline, priority, dependencies
5. **Principal's Personal Brief** — what specifically the Principal must do

### Include for meetings with 3+ participants:
6. **Communication Playbook** — who to message, what to say, when, suggested drafts
7. **Team Dynamics Intelligence** — alliances, tensions, influence patterns, unspoken signals

### Include for strategic/complex meetings:
8. **Topic Deep-Dives** — preliminary research/analysis on discussed topics
9. **Risk and Opportunity Radar** — what could go wrong, what advantages emerged
10. **Strategic Positioning Notes** — how the Principal should position themselves

### Scaling rules:
- **Quick standup** (under 20 min): Sections 1-5 only. 1 page max.
- **Working session** (20-60 min): Sections 1-7. About 2-3 pages.
- **Strategy session** (60+ min or high-stakes): All 10 sections.
- **1:1 meeting**: Sections 1-5 plus section 7.

## Processing Steps

### Step 1: Ingest and Parse
- Read full transcript, identify speakers, determine meeting type, note date/duration/context

### Step 2: Extract Core Intelligence
- **Decisions**: Explicit agreements, approvals, rejections, direction changes
- **Commitments**: Things people said they would do (even casually)
- **Questions left open**: Unresolved items
- **Information shared**: New facts that change the knowledge landscape
- **Emotional signals**: Frustration, enthusiasm, hesitation patterns

### Step 3: Build Action Map
For each item assigned to or relevant to the Principal:
- What exactly needs to be done (specific, not vague)
- Priority: Critical / Important / Nice-to-have
- Deadline (inferred or explicit)
- Dependencies
- One-liner on WHY this matters

### Step 4: Draft Communication Playbook
For each follow-up: what to communicate, suggested channel, timing, draft message skeleton.

### Step 5: Analyze Dynamics and Strategy
Who drove the meeting? Visible tensions? What wasn't said? How is the Principal perceived? Opportunities to build alliance or de-risk?

### Step 6: Deep-Dive on Key Topics
Brief analysis or background for topics that need more context. Flag items requiring further research.

### Step 7: Compile and Output
Calibrate depth to meeting type. Write in the transcript's dominant language.

## Quality Principles

- **Be specific, not generic.** "Send Arkadiusz a Slack message confirming the architecture doc is ready" beats "follow up with Arkadiusz."
- **Infer what's unsaid.** Deflections, casual deadlines, unspoken tensions.
- **Prioritize ruthlessly.** Make it crystal clear what's urgent vs. what can wait.
- **Write for action, not archives.** Every sentence should inform a decision or prompt an action.
- **Protect the Principal's interests.** Be candid about dynamics, risks, and political considerations.