# Screenpipe Meeting Follow Up

Capture decisions and commitments after a meeting and draft a concise follow-up.

- Repository: https://github.com/screenpipe/screenpipe (22202 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add screenpipe/screenpipe --skill screenpipe-meeting-follow-up -g -a claude-code -y`
Codex: `npx skills add screenpipe/screenpipe --skill screenpipe-meeting-follow-up -g -a codex -y`
Cursor: `npx skills add screenpipe/screenpipe --skill screenpipe-meeting-follow-up -g -a cursor -y`
Gemini CLI: `npx skills add screenpipe/screenpipe --skill screenpipe-meeting-follow-up -g -a gemini-cli -y`

## Description

Capture decisions and commitments after a meeting and draft a concise follow-up.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# meeting follow up

Identify the exact meeting and inspect its note or bounded transcript using screenpipe-api. Keep stated intent, agreed work, and completed work separate.
Notes may mix a preparation agenda, generated summary, and older material. Confirm decisions and commitments against the selected meeting's transcript; label anything supported only by the agenda as a proposal. Check speaker identity before assigning an owner, and count repeated audio captures as one utterance.
Write the outcome, decisions, owners, due dates explicitly mentioned, and open questions. Do not invent owners or dates. Include a source link and flag gaps in recording.
Draft a short follow-up when requested. Check the user’s current casing and punctuation preferences. Sending, updating external systems, or creating calendar events requires the user’s explicit request.