agentleFS
Sign inStart free
lexvalolexvalo/riverscript-claude-plugin/skills/interview-notes/SKILL.md

interview-notes

Skill0 starsChanged 42 days agoMITView on GitHub

Turn recorded interviews into structured notes, and compare several of them. Use for customer and user interviews, candidate interviews, research sessions and expert calls, and when the user asks what people said about a topic across conversations.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the person's words separate from the reading of them.

    line 13
  2. Distinctive:

    When a transcript is a translation made in RiverScript, say so where you quote it: the wording is the translator's, not the speaker's.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

An interview is worth more as structure than as prose, and worth most when it can be compared with the others.

  1. Find the interview with list_transcripts when the user names it, or search_transcripts when they describe what was discussed. For a candidate or a customer, their name is usually said out loud and searchable.
  2. Fetch it with get_transcript and read it whole. Interviews turn on wording, hesitation and what a person returned to twice, and a search passage loses that.
  3. Produce notes in the shape the user asked for. When they did not ask for a shape, use: what the person wants, what gets in their way today, what they do instead, and quotes worth keeping, verbatim and marked as quotes.
  4. For a comparison, fetch each interview and answer question by question rather than person by person, so the agreement and disagreement are visible in one place. Name who said what.

Keep the person's words separate from the reading of them. A quote and a conclusion look alike in a summary and matter very differently to the person deciding on it.

When a transcript is a translation made in RiverScript, say so where you quote it: the wording is the translator's, not the speaker's.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free