agentleFS
Sign inStart free
henrique-simoeshenrique-simoes/Istara/skills/discover/user-interviews/SKILL.md

user-interviews

Skill15 starsChanged 47 days agoMITView on GitHub

Plan, conduct, and analyze user interviews. Generate interview guides, process transcripts, extract nuggets and themes, synthesize findings.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always record with consent

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

User Interviews

Capabilities

  • Generate semi-structured interview guides from research questions and project context
  • Process interview transcripts (TXT, PDF, DOCX) — extract nuggets, themes, patterns
  • Identify follow-up questions and research gaps
  • Synthesize findings across multiple interviews with cross-cutting themes
  • Calculate intercoder reliability when multiple coders are involved

Workflow

  1. Plan — Provide research questions → receive interview guide with probes
  2. Conduct — Use the guide (Istara provides facilitation tips)
  3. Upload — Drop transcript files into the project
  4. Analyze — Istara extracts nuggets, tags themes, scores confidence
  5. Synthesize — Cross-interview patterns → facts → insights → recommendations

Input

  • Research questions (text)
  • Interview transcripts (TXT, PDF, DOCX, MD)
  • Project context (auto-loaded from context layers)

Output

  • Interview guide (Markdown)
  • Nuggets with source references and timestamps
  • Thematic analysis with strength indicators
  • Pain points with severity ratings
  • Synthesis report with cross-cutting themes and evidence chains

Best Practices

  • 5-8 participants per segment for saturation
  • 45-60 min per session
  • Always record with consent
  • "Tell me more" > "Did you like it?"
  • Probes yield the best insights, not scripted questions

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.

Check your setup, free