Analyze a Granola meeting into an evidence-backed briefing, decisions, findings, patterns, actions, and continuity. Use for /meeting, /meeting sync, /meeting backfill, or requests to process a meeting.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Acquire meeting material, adapt the analysis to the user's intent, preview the result, then persist one approved typed package through Egregore Runtime.
Read references/analysis-contract.md before analysis or package construction.
Analyze a Granola meeting or supplied transcript into an evidence-backed briefing, decisions, findings, patterns, actions, and continuity. Use for /meeting, /meeting sync, /meeting backfill, or requests to process a meeting.
When the user supplies a transcript as pasted text or a file path, analyze it
directly. Take title, date, and attendees from the user or the file; ask only
for missing metadata needed for analysis or writeback. In the Runtime package,
use source type transcript and preserve a supplied stable source ID when
available; otherwise derive the ID as transcript:<sha256> from the acquired
transcript. Use its SHA-256 for content_hash and, when no source revision is
supplied, for revision. This path does not require Granola.
The Granola connector is required only to list, search, or fetch meeting material. Use the configured Granola connector to list/search meetings and fetch the selected transcript plus title, date, attendees, source ID, and source revision. Do not copy connector credentials or raw transcripts into canonical memory.
/meeting: list recent candidates and let the user choose./meeting <search>: select an exact result or ask when ambiguous./meeting sync: process selected new candidates with balanced defaults./meeting backfill: re-analyze selected canonical meeting sources; never
overwrite newer claims without explicit supersession.If Granola is unavailable, explain the connection issue and stop. Connector access is source acquisition, not organizational authorization or canonical writeback.
Reuse sufficient EGREGORE_ORG_CONTEXT_V1. Open already-selected canonical
evidence through the Runtime source-open boundary when exact verification is
needed. Do not repeat Observe/search merely because this skill loaded.
If compiled context is insufficient and continuity materially matters, make at most one Egregore retrieval call, then open only relevant canonical sources. Never query graph/QMD directly. Canonical Markdown/Git wins on disagreement.
For one interactive meeting, ask briefly what matters and whether the user wants quick extraction or deeper dynamics/continuity. Skip questions when the request already specifies intent, and in sync/backfill mode.
Choose only useful lenses from the reference. Inline analysis is the fast default; parallel analysts are optional for long or complex transcripts. Actions remain separate from durable decisions/findings/patterns.
Show a concise preview with the heart of the meeting, evidence, confidence,
relationships, tensions, and actions. Ask Save, Edit, or Skip. Do not
write before Save.
Build one temporary egregore-research-ingest/v1 package under tmp/ from the approved
briefing and extracted artifacts, then make exactly one deterministic call, using
{package-json} for the package file just written:
bash bin/research-ingest.sh meeting --input '{package-json}'
Runtime owns authorization, schema/path validation, stable identity,
provenance, canonical Markdown, Git provenance, derived-index refresh,
background embedding, and telemetry. Do not separately write files, mutate a
processed-meetings cache, run /save, or manage graph projection.
Report accepted/partial/rejected status and canonical paths from the receipt. Graph projection, publication, and notifications are optional later effects. Each requires its own capability/permission boundary; publication and every notification also require a separate exact user approval.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
The English summary is being prepared. Showing the original description.
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
The English summary is being prepared. Showing the original description.
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
The English summary is being prepared. Showing the original description.
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
The English summary is being prepared. Showing the original description.
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
The English summary is being prepared. Showing the original description.
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
The English summary is being prepared. Showing the original description.