agentleFS
egregore-labsegregore-labs/egregore/.claude/skills/ingest-user-interview/SKILL.md

ingest-user-interview

Skill293 starsChanged 10 days agoMITView on GitHub

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 file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read references/analysis-contract.md before analysis or package construction.

    line 12
  2. Very specific:

    Use the meeting skill for a general team meeting.

    line 19
  3. Distinctive:

    Start with a compact scaffold.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ingest user interview

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.

When to invoke

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.

Source

Accept one of:

  • Granola connector: search/select, then fetch transcript and stable metadata;
  • pasted transcript;
  • a user-authorized .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.

Context and analysis

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.

Canonical writeback

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.