pavilio-note-batch

Batch-processes unprocessed Quill meeting transcripts into project notes via fan-out subagents.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-note-batch-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-note-batch
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-note-batch
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-note-batch-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Processing meeting transcripts one at a time is slow and repetitive when several unprocessed Quill meetings pile up. This Skill discovers all unprocessed meetings, guesses each one's owning project, and processes up to five of them in a single orchestrated run with one combined Todoist selection and one git commit. ## Core Features & Use Cases - Discovery and deduplication: Reads the processed-transcripts registry and verifies notes on disk, backfilling stale registry entries so no meeting is processed twice. - Project guessing: Scores transcripts against project search keywords and team member names to suggest the owning project with a confidence level, with user override support. - Parallel fan-out: Spawns subagents running the pavilio-note skill in batch mode, parallel across projects and sequential within a project to avoid file conflicts. - Use Case: After a week of meetings, run the batch command to see five unprocessed meetings with guessed projects, confirm which to process, and get notes written, todos pushed to Todoist, and everything committed in one go. ## Quick Start Ask the agent to process all unprocessed meetings and then pick the numbered meetings you want handled.

Frequently Asked Questions about pavilio-note-batch

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

FAQPage Schema
How do I process multiple meeting transcripts at once?▼

Invoke the batch command to list up to five unprocessed Quill meetings with guessed projects, then reply with the numbers to process. Each selected meeting is handled by a subagent that writes the note, and results are aggregated into one commit.

How does meeting-to-project matching work with transcripts?▼

A scout subagent counts case-insensitive keyword occurrences from each project's search keywords, team names, and folder name against the transcript. The highest score wins, with confidence rated high, med, low, or unknown based on hit counts.

Can I override the guessed project for a meeting?▼

Yes, reply with N:project to override the guess for meeting number N. Meetings with no confident guess require an explicit project assignment, and bare numbers with unknown guesses are skipped.

Does batch processing skip meetings that already have notes?▼

Yes, the scout checks both the processed-transcripts registry and the note directories on disk for matching date and time filenames. Meetings with existing notes are backfilled into the registry instead of being offered for processing.

What happens if a meeting processing subagent fails?▼

A failed subagent does not stop the others. The failure is reported with the meeting title and reason, its temporary transcript is kept for retry, and its registry entry is not appended.