SkillAgentSearch skills...

minutes-ingest

Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index

Install / Use

npx skills add silverstein/minutes --skill minutes-ingest

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of minutes-ingest

minutes-ingest scores 86/100 on our quality scale, 1803rd of 2,790 Automation skills we index.

Its SKILL.md is 3.5 KB long, well organised into 10 sections with 5 code examples: a solid amount of guidance for an agent.

With 1,500 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so minutes-ingest is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

minutes-ingest compared with similar skills

All 4 of these similar skills score higher than minutes-ingest; compare them before choosing.

SkillScoreStarsUpdatedFormat
minutes-ingest (this skill)by silverstein861.5k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install minutes-ingest?
Run npx skills add silverstein/minutes --skill minutes-ingest. The install tabs above show the steps for each supported agent.
Which AI agents does minutes-ingest work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is minutes-ingest safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is minutes-ingest still maintained?
The repository was last updated about 2 months ago, so minutes-ingest is actively maintained.

name: minutes-ingest description: Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data. compatibility: opencode

/minutes-ingest

Process meetings through the knowledge extraction pipeline to update person profiles, append to the knowledge log, and maintain the index.

Prerequisites

The [knowledge] section must be configured in ~/.config/minutes/config.toml:

[knowledge]
enabled = true
path = "/path/to/knowledge/base"
adapter = "wiki"  # or "para", "obsidian"
engine = "none"   # or "agent" for LLM extraction
min_confidence = "strong"

If not configured, explain what's needed and offer to help set it up.

How to run

Single meeting

minutes ingest ~/meetings/2026-04-03-strategy-call.md

All normal meetings (backfill)

minutes ingest --all

Preview without writing (recommended first time)

minutes ingest --all --dry-run

What it does

  1. Reads each meeting's YAML frontmatter (decisions, action_items, entities, intents)
  2. Extracts structured facts with confidence levels and source provenance
  3. Updates person profiles in the knowledge base (adapter-dependent format)
  4. Appends to log.md with a timestamped entry for each ingested meeting
  5. Skips facts that already exist (deduplication) or are below the confidence threshold
  6. Excludes meetings designated sensitivity: restricted from automated knowledge-base ingestion

Safety guarantees

  • engine = "none" (default): Only extracts from parsed YAML frontmatter. No LLM involved, zero hallucination risk.
  • Confidence thresholds: Facts below min_confidence are counted as "skipped" but never written.
  • Provenance: Every fact records which meeting it came from and when.
  • Deduplication: Facts whose text already appears in a person's profile are skipped.
  • Dry-run: Always suggest --dry-run first if the user hasn't used ingest before.

Interpreting the output

Ingesting 73 meeting(s) into knowledge base at /path/to/kb
  2026-04-03-strategy.md — 4 written, 1 skipped — Mat, Dan
  2026-04-05-standup.md — 2 written, 0 skipped — Alice
  SKIP 2026-03-18-test.md: no frontmatter

Done. 6 fact(s) written, 1 skipped, 1 error(s), 3 people updated.
  • written: facts that passed confidence threshold and didn't already exist
  • skipped: facts below confidence threshold (logged, not written)
  • SKIP: files that couldn't be parsed (no frontmatter, invalid YAML, etc.)

Gotchas

  • Meetings without summarization have no structured data — If a meeting was recorded before summarization was enabled, its frontmatter won't have action_items or decisions. The ingest will correctly extract 0 facts. This is expected, not an error.
  • engine = "agent" requires an AI CLI — If the user wants richer LLM-based extraction from transcript body text, they need claude, codex, gemini, opencode, or pi on PATH.
  • PARA adapter writes items.json — If the user's knowledge base uses the PARA format, facts go into areas/people/{slug}/items.json with atomic fact schema (id, status, supersededBy).
  • First run should be dry-run — Always suggest minutes ingest --all --dry-run before the first real run so the user can see what would be extracted.

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryAutomation
Updated1mo ago
Forks165

Languages

Rust

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions