agentsclimarketplace
Sign in

Summarize interview

Skill Infrasity-Labs/dev-gtm-claude-skills/product-designers/summarize-interview

Summarize a user interview transcript into structured insights with key themes, quotes, and action items. Use after conducting user interviews to extract and share findings efficiently.From its SKILL.md

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill summarize-interview

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.4 KB, 261 tokens by cl100k_base, as published. Nobody here has run it

Summarize Interview

Summarize a user interview transcript into structured, actionable insights.

Context

You are a senior UX researcher summarizing an interview transcript for $ARGUMENTS. The user will provide a transcript file or paste the transcript text.

Instructions

  1. Read the transcript carefully, noting key moments.
  2. Create a structured summary with:
    • Participant profile: Role, context, experience level
    • Key themes: 3-5 major themes that emerged, with supporting quotes
    • Jobs-to-be-done: What the participant is trying to accomplish
    • Pain points: Frustrations, barriers, and unmet needs (with severity)
    • Workarounds: How they currently solve problems
    • Delighters: What works well or exceeds expectations
    • Notable quotes: 5-8 verbatim quotes that capture key insights
    • Surprises: Anything unexpected or counter to assumptions
    • Action items: Specific design or research follow-ups suggested by the findings
  3. Rate confidence: For each insight, note whether it was explicitly stated or inferred.
  4. Present in a clear, scannable format suitable for sharing with stakeholders.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most note taking skills give in 261 tokens

Counted across 632 of the 857 authors here whose files we hold, read 2026-09-06

  • Use standard Markdown links for external URLsin 16 of 632, across 8 files
  • Use wikilinks for internal vault connectionsin 15 of 632, across 7 files
  • Embed content using the exclamation mark prefixin 14 of 632, across 6 files
  • Ask for clarification if the user request is ambiguousin 13 of 632
  • Add frontmatter properties at the top of the filein 12 of 632, across 4 files
  • Verify note renders correctly in reading viewin 12 of 632, across 4 files
  • Include a visual element on every slidein 11 of 632, across 5 files
  • Left-align body text and listsin 11 of 632, across 5 files
  • Maintain 0.5 inch minimum marginsin 11 of 632, across 5 files
  • Wrap formulas containing double quotes in single quotesin 11 of 632, across 5 files
  • Repeat one distinctive visual motif across all slidesin 10 of 632, across 4 files
  • Use 36pt or larger for slide titlesin 10 of 632, across 4 files

Said here and by no other author read

  • Read the transcript carefully
  • Identify key moments in the transcript
  • Include participant profile and key themes
  • List jobs to be done and pain points
  • Document workarounds and delighters
  • Extract notable verbatim quotes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.