summarize-interview
Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- summarize-interview
- description
- Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档agents/openai.yaml43 B
- 参考文档CREDITS.md349 B
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
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
- Read the transcript carefully, noting key moments.
- 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
- Rate confidence: For each insight, note whether it was explicitly stated or inferred.
- Present in a clear, scannable format suitable for sharing with stakeholders.
04 同仓库更多 Skills
explainroo
Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.
unslop
Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".
technical-writing
Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.