minutes-ingest

Ingest meetings to extract structured facts and update knowledge bases.

Updated May 23, 2026
One-click install
npx skills add https://github.com/jacob-split/minutes --skill minutes-ingest-jacob-split
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minutes-ingest
Source: https://github.com/jacob-split/minutes/tree/main/.agents/skills/minutes/minutes-ingest
Command: npx skills add https://github.com/jacob-split/minutes --skill minutes-ingest-jacob-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest meetings to extract structured facts and update the knowledge base with person profiles, a chronological log, and an index.

Core Features & Use Cases

  • Ingest single meetings or backfill from multiple meetings into a knowledge base, preserving provenance and deduplicating facts.
  • Update person profiles and append to a chronological log to maintain a memory of decisions and actions.
  • Support adapters (wiki, para, obsidian) and provide safe, dry-run options before writing changes.

Quick Start

Instruct Minutes to ingest the latest meeting file to update your knowledge base.

Frequently Asked Questions about minutes-ingest

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

FAQPage Schema
How do I extract facts from meeting notes to update a knowledge base?

Yes, you can backfill multiple meetings into a knowledge base by running a bulk ingestion process. This preserves provenance, applies deduplication to avoid repeated facts, and appends all historical data to a chronological log safely.

Does meeting ingestion work with Obsidian and wiki-style knowledge bases?

Yes, meeting ingestion works with Obsidian, Para, and wiki-style knowledge bases through configurable knowledge adapters. These adapters allow ongoing syncs and enable targeted updates to person profiles and indexes within your existing structure.

Can I preview changes to person profiles before writing to my knowledge base?

Yes, you can preview changes to person profiles by using the dry-run feature before writing to your knowledge base. This safe mode shows the extracted facts and profile updates without applying any destructive modifications.

How does meeting fact deduplication work when syncing ongoing notes?

Meeting fact deduplication works during ongoing syncs by tagging provenance and checking new facts against existing knowledge base entries. This prevents duplicate records while maintaining a chronological log of decisions and actions.

What is the best way to maintain a chronological log of decisions from meeting notes?

The best way to maintain a chronological log of decisions is to ingest meetings using frontmatter-driven extraction. This automatically appends structured facts and actions to your log while updating person profiles and preserving data provenance.