Meeting Intel

Turn a raw meeting transcript into structured, owned, dated follow-through.

Distilled from a pipeline that polls Fathom for recordings, extracts action items with Claude, and creates Linear tasks automatically. This skill is the extraction and task-creation core, made source-agnostic.

Inputs

Accept any of: pasted transcript text, a file path, a Fathom/Zoom/Meet summary, or rough typed notes. If the input is missing attendee names, ask once for them; otherwise never block on questions.

Workflow

1. Read the full transcript before extracting anything.
2. Extract into three buckets, strictly separated:
   • Decisions - things that were settled. Past tense, one line each, with who made the call if identifiable.
   • Action items - each MUST have an owner and a due date. If the transcript states neither, infer the owner from context and mark the date (proposed) with your best inference. Never emit an ownerless action item; assign it to the user and flag it.
   • Open questions - raised but not resolved. These are the follow-up agenda for next time.
3. Discard filler: status updates with no consequence, small talk, scheduling chatter. A 60-minute meeting typically yields 3-8 action items. If you extracted 20, you are transcribing, not extracting.
4. Create the action items in the user's tracker, in this order of preference: a connected task MCP tool (Linear, Asana, Todoist, etc.) if available in the session; otherwise the project's TODO/tasks file if one exists; otherwise output a markdown task block.
5. When creating tracker tasks: title is the action, description carries the transcript quote that generated it, owner and due date set as extracted. Never create duplicates - search the tracker for similar open tasks first.

Output format

## Meeting: <title or best inference> - <date>

### Decisions
- <decision> (<who>)

### Action items          [created in <tracker> / markdown only]
- [ ] <action> - @<owner>, due <date>

### Open questions
- <question>

Anti-patterns

• Do not summarize the meeting. This skill extracts commitments, not vibes.
• Do not soften ownership: "the team will look into it" becomes a named owner or a flagged item, never a shared vague one.
• Do not invent action items from suggestions nobody agreed to.