meeting-ingestion

Ingest meeting transcripts into structured knowledge graph pages with entity enrichment.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Ninatuzi/gbrain --skill meeting-ingestion-ninatuzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meeting-ingestion
Source: https://github.com/Ninatuzi/gbrain/tree/main/skills/meeting-ingestion
Command: npx skills add https://github.com/Ninatuzi/gbrain --skill meeting-ingestion-ninatuzi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented meeting information by automatically parsing transcripts into structured, interconnected knowledge pages that link people, companies, and action items.

Core Features & Use Cases

  • Automated Entity Enrichment: Automatically creates or updates people and company pages based on meeting participants and mentions.
  • Timeline Integration: Merges meeting events into the timelines of all mentioned entities for a comprehensive history.
  • Use Case: After a sales call, use this skill to instantly generate a meeting summary, assign action items to the correct stakeholders, and ensure the company and attendee profiles are updated with the latest context.

Quick Start

Process the meeting transcript provided in the current context to update the brain with new attendees and action items.

Frequently Asked Questions about meeting-ingestion

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

FAQPage Schema
How do I convert meeting transcripts into a structured knowledge graph?

Meeting transcripts are converted into a structured knowledge graph by automatically parsing raw text into interconnected pages with automated entity enrichment, timeline propagation, and bidirectional back-linking across people and company domains.

How do I automate entity extraction from meeting transcripts for people and company pages?

Entity extraction from meeting transcripts is automated by identifying participants and mentions to instantly create or update people and company pages, ensuring all profiles receive the latest context through timeline integration.

Do I need search and page-writing tools to maintain a knowledge base from meeting transcripts?

Yes, integrating search, query, and page-writing tools is required to maintain a self-wiring knowledge base, as the process relies on these tools to propagate timeline events and ensure bidirectional data consistency across domains.

What is the best way to link meeting action items to stakeholders in a knowledge graph?

Linking meeting action items to stakeholders is best handled by ingesting raw transcripts to automatically assign items to the correct people and companies, merging events into entity timelines for comprehensive history.

Can I use this transcript parsing approach for sales calls to update attendee and company profiles?

Yes, this approach supports sales calls by instantly generating meeting summaries, assigning action items to stakeholders, and ensuring attendee and company profiles are updated with the latest context.

Why does meeting transcript ingestion require bidirectional back-linking across domains?

Bidirectional back-linking across meeting, people, and company domains is required during transcript ingestion to ensure data consistency and maintain a self-wiring knowledge base with comprehensive timeline history.