meeting-ingestion

Classifies meeting transcripts from Google Drive, Pocket, and uploads into structured intelligence blocks via Zo API.

5|Updated Jan 15, 2026

Search Tags:#transcripts #crm-routing #meeting-ingestion #intelligence-blocks #zo-take-heed #drive-ingestion

Ready to run

npx skills add https://github.com/thevibethinker/n5os-ode --skill meeting-ingestion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meeting-ingestion
Source: https://github.com/thevibethinker/n5os-ode/tree/main/Skills/meeting-ingestion
Command: npx skills add https://github.com/thevibethinker/n5os-ode --skill meeting-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Meeting transcripts from multiple sources are scattered and hard to classify, summarize, and route for follow-up.

Core Features & Use Cases

Ingests transcripts from Google Drive, Pocket, and manual uploads and normalizes them into a consistent intake format.
Classifies content type (meeting vs reflection) and generates structured intelligence blocks for downstream processing.
Routes and archives items to appropriate downstream destinations with optional CRM integration.

Quick Start

Run the unified CLI to pull transcripts, process them, and route results into your workspace.

Frequently Asked Questions about meeting-ingestion

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

FAQPage Schema

How do I automatically classify and normalize meeting transcripts from Google Drive?▼

Meeting ingestion normalizes transcripts from Google Drive, Pocket, and manual uploads into a consistent intake format, then automatically classifies content types like meetings versus reflections for downstream processing.

Can I route processed meeting transcripts to a CRM using a unified CLI?▼

Yes, meeting ingestion supports optional CRM integration to route and archive classified items to appropriate downstream destinations using a unified CLI and supporting scripts.

How do I generate structured intelligence blocks from multi-source meeting transcripts?▼

Meeting ingestion generates structured intelligence blocks by classifying normalized transcripts and processing them via a Zo API, coordinating ingestion, classification, and block generation in one workflow.

Do I need pyyaml and requests to run meeting transcript ingestion and archival scripts?▼

Yes, pyyaml and requests are required dependencies for running the unified CLI scripts that coordinate transcript ingestion, manifest generation, block generation, and weekly folder archival.

What is the best way to archive classified meeting transcripts into weekly folders?▼

The unified CLI archives classified meeting transcripts into weekly folders during the routing phase, coordinating with manifest generation and ZTH scanning to ensure structured archival.

Are there limitations when manually uploading meeting transcripts for classification and block generation?▼

Manual uploads are supported alongside Google Drive and Pocket sources, but transcripts must fit the normalized intake format to enable proper classification, block generation, and CRM routing.