meeting-ingest

Sanitize meeting transcripts and extract structured decisions, actions, and feedback.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Nikhil-Chopra-7/claude-frontend-skills --skill meeting-ingest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meeting-ingest
Source: https://github.com/Nikhil-Chopra-7/claude-frontend-skills/tree/main/meeting-ingest
Command: npx skills add https://github.com/Nikhil-Chopra-7/claude-frontend-skills --skill meeting-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Meeting Ingest skill turns raw meeting transcripts or notes into a clean, structured meeting-context document that captures decisions, scope changes, PRD/design feedback, open questions, action items, new constraints, and unresolved disagreements. It preserves speaker attribution and provides a reproducible artifact to feed companion context into the feature-build process.

Core Features & Use Cases

  • Sanitization pass: cleans transcripts by removing filler, correcting transcription errors, and preserving speaker labels.
  • Delta extraction: outputs decisions, scope changes, feedback, questions, actions, and constraints with source quotes.
  • Companion-context delivery: produces a document that augments the PRD/design context at feature-build time.
  • Standalone utility: usable when presenting meeting outcomes separately from the PRD or design review.

Quick Start

Paste the meeting transcript (or transcript file) and, when available, the PRD and Figma references; I will sanitize and extract a structured meeting-context document.

Frequently Asked Questions about meeting-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract action items and decisions from raw meeting transcripts?▼

To extract action items from raw meeting transcripts, you paste the transcript text to trigger a sanitization pass that outputs a structured document capturing decisions, feedback, and action items with source quotes.

What is the best way to structure PRD scoping meeting notes?▼

The best way to structure PRD scoping meeting notes is to process raw transcripts through a two-stage pipeline that sanitizes content and extracts a structured document capturing decisions, scope changes, and PRD feedback.

Can I use meeting notes to capture PRD and design feedback separately from the main document?▼

Yes, you can use the extraction process as a standalone utility to capture PRD and design feedback separately, producing a companion-context document that augments the main PRD at feature-build time.

Does the meeting context extraction preserve speaker labels from the original transcript?▼

Yes, the extraction process preserves speaker attribution. The sanitization pass cleans the raw transcript by removing filler and correcting errors while explicitly maintaining the original speaker labels.

How do I sanitize raw meeting output to remove filler and transcription errors?▼

You sanitize raw meeting output by running it through a dedicated cleaning pass that removes filler words and corrects transcription errors, resulting in clean text that retains speaker labels and source quotes for delta extraction.

Do I need to provide a PRD and Figma references to extract meeting context?▼

No, providing a PRD and Figma references is optional. The extraction works with just the raw meeting transcript, but including these references enhances the companion-context document for feature-build time.