Analyze a user interview from Granola, pasted text, or a file into an evidence-backed briefing, journey insights, product findings, patterns, and actions. Use for /ingest user-interview, onboarding interviews, research calls, or requests to process user feedback.
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 the transcript, understand the research intent, analyze it with appropriate lenses, preview the result, then persist one approved typed package through Egregore Runtime.
Read references/analysis-contract.md before analysis or package construction.
Analyze a user interview from Granola, pasted text, or a file into an evidence-backed briefing, journey insights, product findings, patterns, and actions. Use for /ingest user-interview, onboarding interviews, research calls, or requests to process user feedback.
Use the meeting skill for a general team meeting.
Accept one of:
.txt, .md, or .json file.Infer participant, researcher, interview type, date, and source revision when reliable; otherwise ask compact questions. Do not put connector credentials or the raw transcript into canonical memory merely to analyze it.
Reuse sufficient EGREGORE_ORG_CONTEXT_V1. Open selected canonical evidence
through Runtime when verification is necessary. If cross-interview comparison
is requested and context is insufficient, make at most one Egregore retrieval
request. Never query graph/QMD directly; canonical Markdown/Git wins.
Start with a compact scaffold. Analyze inline for short interviews. For long or complex material, parallel Journey, Sentiment, and Product lenses may run once, then synthesize their evidence and disagreements. Do not force multi-agent work when it adds latency without analytical value.
Show the emotional arc, evidence-backed product reading, proposed durable
insights, confidence, priority, tensions, and researcher actions. Ask Save,
Edit, or Skip. Do not write before Save.
Build one temporary egregore-research-ingest/v1 package under tmp/ containing the
approved interview briefing, participant journey document where needed, and
typed findings/patterns/decisions. Then make exactly one deterministic call, using
{package-json} for the package file just written:
bash bin/research-ingest.sh interview --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 create directories,
append indexes, write files, run /save, or manage graph projection.
Report accepted/partial/rejected status and canonical paths. Cross-interview synthesis reads canonical artifacts; graph is optional enrichment only. Publication and notifications are separate later effects and require their own explicit 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.