analyze-interviews
Skill9 starsChanged 4 months agoNo licenceView on GitHub
Takes one or many customer-interview files you already have and reconstructs the Jobs To Be Done structure hiding inside them. Asks which business task you are solving, then reads each interview in its own subagent (so large transcript sets never overflow context), assigns each interview an honest confidence and a quality read, clusters the extractions into segments by Core Jobs, computes a confidence level per segment, and writes one report covering data quality, segments and personas, current Solutions and their Problems, the Consideration Set per segment, value hypotheses, and what to interview next. Two modes: Quick (offline) and Deep (web-enriched). This is the after-fieldwork counterpart to the interview-guide flow.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- improveSkill
- advisorSkill
- anti-best-practiceSkill
- brainstormingSkill
- caveman-distillateSkill
- ce-ideateSkill
- claude-md-improverSkill
- code-modernizationSkill
- command-creatorSkill
- decision-matrixSkill
- diagnoseSkill
- docxSkill
- go-to-marketSkill
- grill-meSkill
- humanizerSkill
- improve-codebase-architectureSkill
- karpathy-guidelinesSkill
- market-researchSkill
- orchestrateSkill
- pdf-creatorSkill
- planningSkill
- product-requirementsSkill
- report-writerSkill
- security-scanSkill
- session-reportSkill
- spec-normalizerSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- ui-first-principlesSkill
- ui-ux-pro-maxSkill
- value-propSkill
- verification-passSkill
- webapp-testingSkill
- workflow-plannerSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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
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.

