pavilio-note

Convert meeting transcripts into structured project notes, status files, and decision logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning raw meeting transcripts into consistent, searchable project knowledge is tedious and error-prone. This Skill processes a transcript into structured notes, keeps STATUS.md, DECISIONS.md, and a machine-readable _index.json up to date, and proposes Todoist follow-up tasks. ## Core Features & Use Cases - Transcript-to-notes pipeline: Fetches meetings from Quill/Fathom MCP (with a processed-transcripts registry to prevent duplicates) or accepts manual paste, then generates a detailed summary with decisions, proposals, open questions, and action items with transcript anchors. - Project knowledge maintenance: Rewrites STATUS.md with enforced section caps, appends decided items to DECISIONS.md, updates PROJECT.md only when stable facts change, and merges entities into _index.json for LLM search. - Participant recognition and task follow-up: Maps speaker labels to known participants, confirms them with the user, and offers selected action items as Todoist tasks. - Use Case: After a daily standup recorded in Quill, invoke the skill to produce a Polish-language structured note, refresh the project's volatile status, log new decisions, and push the changes to git. ## Quick Start Run /pavilio-note and tell the agent which project and meeting transcript to process.

Frequently Asked Questions about pavilio-note

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

FAQPage Schema
How do I turn a meeting transcript into structured notes?▼

Invoke /pavilio-note with a project name, then pick a recent meeting from Quill MCP or paste the transcript manually. The skill generates a detailed summary note, saves the verbatim transcript, and updates the project's status and index files.

How does the skill distinguish decisions from proposals?▼

Each extracted item gets a modality: decided, tentatively agreed, or proposed. Only decided items are written to DECISIONS.md and the index; proposals stay in the note with who raised them and what would make them a decision.

Can it fetch transcripts from Quill or Fathom automatically?▼

Yes. It lists recent meetings from the Quill MCP, filters out any already recorded in the .processed_transcripts.json registry, and falls back to manual paste if the MCP is unavailable. The same deduplication logic applies to Fathom or other transcript MCPs.

How are unknown speakers in a transcript handled?▼

The skill maps Speaker 1/2/3 labels using the known_participants list in _index.json and asks the user to confirm identified participants. It never invents names; unidentified speakers remain as Speaker X until the user clarifies.

What happens if the generated STATUS.md exceeds its section caps?▼

A post-write check counts bullets and rows per section rather than eyeballing them. In -yolo or batch mode, exceeding a cap produces a status: error result instead of a silent success, so the note must be fixed.