dotfiles/dot_config/skillshare/skills/summarize-interview/SKILL.md
Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries.
npx skillsauth add pkking/dotfiles summarize-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.
You are summarizing a customer interview for the product discovery of $ARGUMENTS.
The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first.
Read the full transcript carefully before summarizing.
Fill in the summary template below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied").
Use clear, simple language — a primary school graduate should be able to understand the summary.
**Date**: [Date and time of the interview]
**Participants**: [Full names and roles]
**Background**: [Background information about the customer]
**Current Solution**: [What solution they currently use]
**What They Like About Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]
**Problems With Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]
**Key Insights**:
- [Unexpected findings or notable quotes]
**Action Items**:
- [Date, Owner, Action — e.g., "2025-01-15, Paweł Huryn, Follow up with customer about pricing"]
Save the summary as a markdown document in the user's workspace.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
development
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.