meeting-ingestion

Ingest meeting transcripts into knowledge-base pages with attendee enrichment and verification.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill meeting-ingestion-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meeting-ingestion
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/meeting-ingestion
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill meeting-ingestion-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Meeting transcripts from recorders arrive messy: anonymous speaker labels, garbled names, AI summaries that confabulate facts, and recordings that contain multiple meetings. This Skill normalizes any recorder's output into a standard transcript record and runs a unified pipeline that turns it into verified, cross-linked knowledge-base pages instead of raw notes. ## Core Features & Use Cases - Unified ingestion pipeline: Normalize transcripts from any meeting recorder, split multi-meeting recordings, dedupe across recorders, and resolve speakers by evidence rather than guesswork. - Claim verification and consistency checks: Treat recorder summaries as claims, verify surprising claims against the transcript, existing brain pages, and plausibility before writing them to entity pages. - Enrichment and verification gate: Create or update people and company pages, merge timeline entries across all mentioned entities, and block completion until a six-part checklist (including sequence verification) passes. - Use Case: After a Granola or Circleback recording of a pitch meeting, run the pipeline to produce a structured meeting page with verbatim quotes, enriched attendee pages, timeline entries on every mentioned company, and a report confirming all checks passed. ## Quick Start Ingest this meeting transcript from my recorder into the brain, enrich every attendee, and run the full verification checklist before reporting it done.

Frequently Asked Questions about meeting-ingestion

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

FAQPage Schema
How do I ingest a meeting transcript into a knowledge base?

Normalize the recorder output into a standard transcript record with attendees, segments, and raw text, then run the pipeline: split detection, dedup, speaker resolution, page creation, claim verification, attendee enrichment, and timeline merge. The meeting is only reported ingested after the verification checklist passes.

How to handle meeting recordings that contain multiple meetings?

Detect split signals like roster shifts, topic hard-cuts, or context resets before creating pages. Partition the transcript into contiguous chunks at the boundaries, run the pipeline once per chunk, and cross-link the resulting sibling pages with the shared source id.

Does this work with recorders like Granola or Circleback?

Yes, the pipeline is recorder-agnostic. Any source — AI notetaker export, webhook payload, share link, or pasted transcript — is normalized into the same transcript record, and source-specific logic ends at normalization.

Why are recorder AI summaries treated as claims instead of facts?

Recorder summaries pass through speech-to-text and AI summarization, and both layers confabulate. Surprising claims like role changes or deal events must be verified against verbatim transcript lines, existing brain pages, and plausibility before being written to entity pages.

What happens when a speaker cannot be identified from the transcript?

The speaker is written as [Room] or UNKNOWN with an explicit uncertainty flag rather than guessed. User-provided ground truth overrides recorder diarization, and low-confidence identifications are never backlinked to person pages.