Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add frank-luongt/faos-skills-marketplace --skill summarize-interviewgit clone --depth 1 https://github.com/frank-luongt/faos-skills-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/frank-luongt/faos-skills-marketplace/summarize-interview)<a href="https://agentmods.dev/skills/frank-luongt/faos-skills-marketplace/summarize-interview"><img src="https://agentmods.dev/badge/skills/frank-luongt/faos-skills-marketplace/summarize-interview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/frank-luongt/faos-skills-marketplace/summarize-interview"><img src="https://agentmods.dev/badge/skills/frank-luongt/faos-skills-marketplace/summarize-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01280 |
| Opus 5 | $0.00000 | $0.00640 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
summarize-interview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: summarize-interview description: Transform customer interview transcripts or notes into structured summaries with JTBD insights, pain points, and action items. Use when processing interview data after customer discovery sessions. tags: [discovery, customer-research, interviews, synthesis]
Summarize Interview
Transform raw interview transcripts or notes into structured, actionable summaries that feed directly into Opportunity Solution Trees, PRDs, and product decisions.
Purpose
Interview transcripts are long, unstructured, and hard to compare across participants. This skill extracts the signal — jobs, pains, outcomes, and surprises — into a consistent format that enables pattern recognition across interviews.
When to Use
- After conducting a customer discovery interview
- When processing a batch of interview transcripts
- When synthesizing research for a product brief or PRD
- When building or updating an Opportunity Solution Tree
Required Input
Provide one of:
- Full interview transcript (text or audio-to-text)
- Detailed interview notes
- Recording summary from a note-taking tool
Output Template
For each interview, produce this structured summary:
# Interview Summary
## Metadata
| Field | Value |
| --- | --- |
| Date | [interview date] |
| Participant | [name or ID] |
| Role / Title | [their role] |
| Company / Context | [company, size, industry] |
| Interviewer | [your name] |
| Duration | [minutes] |
---
## Current Situation
**What they do today:**
[1–3 sentences describing how they currently handle the relevant activity]
**Tools / processes used:**
- [tool or process 1]
- [tool or process 2]
**How long they've done it this way:** [duration]
---
## Jobs to Be Done
For each job identified:
| Job | Importance (1–10) | Current Satisfaction (1–10) | Opportunity Score |
| --- | --- | --- | --- |
| [Job description — what they're trying to accomplish] | [rating] | [rating] | [Importance × (1 − Satisfaction/10)] |
---
## Pain Points
| Pain Point | Severity | Frequency | Current Workaround |
| --- | --- | --- | --- |
| [pain description] | High / Medium / Low | Daily / Weekly / Occasionally | [how they cope] |
---
## Desired Outcomes
- [What "success" looks like in their words]
- [Measurable outcome they care about]
---
## What They Like About Current Solution
- [positive aspect] — why it matters to them
- [positive aspect] — why it matters to them
---
## Willingness to Change / Pay
- **Have they searched for alternatives?** [Yes/No — details]
- **Have they spent money on this?** [Yes/No — how much, on what]
- **Priority vs. other problems:** [High / Medium / Low]
- **Switching cost concern:** [what would make switching hard]
---
## Key Insights
- [unexpected finding 1]
- [unexpected finding 2]
---
## Notable Quotes
> "[exact verbatim quote — the most revealing thing they said]"
> "[another important quote]"
---
## Action Items
| Action | Owner | Due |
| --- | --- | --- |
| [follow-up action from this interview] | [who] | [when] |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 197 lines · 0 tokens per session scan A 163fed096f89
summarize-interview is a skill published in the GitHub repository frank-luongt/faos-skills-marketplace (33 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,280 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
task-observer
Monitors task execution for skill improvement opportunities. Use during ANY multi-step task, agentic workflow, or work session where the agent uses tools and produces deliverables. Captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers in post-task…
resume-tailor
Use when the user has a specific job posting and wants to customize their resume, CV, work document, and/or cover letter for that role. Also use when they say "I'm applying to..." or share a job link.
resume-builder
Use when the user wants to create or update a source work document in resume or CV format, or create a source cover letter from scratch. Triggers on US resumes ("build my resume") and UK/EU-style work CVs ("build my CV", "I need a CV for a UK role", "European CV"). US academic CVs are out of scope. For first-time…
claim-check
Use when the user wants a final truth pass before submitting a resume, CV, cover letter, LinkedIn section, or application package. Also use when they ask whether a draft contains unsupported, inflated, or hallucinated claims.
linkedin-optimizer
Use when the user wants to improve their LinkedIn profile, rewrite their headline, about, or experience sections, or audit individual profile fields.
proof-asset-creator
Use when the user wants to figure out what proof-of-value asset to build — case study, portfolio piece, personal site content, or any artifact that demonstrates their skills to employers. Ideation and scoping only; once an idea is chosen, the user continues in a fresh agent conversation to produce the asset. Triggers…