analyst-@SLUG@

Generates per-interview themes, sentiment, and field notes from tagged transcript lines.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/borderux/recursica-knowledge --skill analyst-slug-borderux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyst-@SLUG@
Source: https://github.com/borderux/recursica-knowledge/tree/main/agents/claire/subagents/analyst
Command: npx skills add https://github.com/borderux/recursica-knowledge --skill analyst-slug-borderux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analyzing user research interviews manually is slow and error-prone: quotes get paraphrased, evidence goes uncited, and single-interview observations get presented as cohort findings. This Skill produces a rigorous, evidence-grounded per-interview write-up where every claim traces to a verified transcript line. ## Core Features & Use Cases - Verified findings pipeline: Writes every finding to BigQuery via write_finding with mandatory verbatim quote evidence, validated line IDs, and honest confidence scores; findings are always written as proposed for human review. - Pass-based transcript reading: Surveys tag summaries first, walks line ranges with compact notes, and verifies every citation with a dedicated tool before writing, with measured coverage reporting. - Structured field notes: Produces a sub-500-word Google Doc with 3-4 themes (each resting on 2+ tagged lines), sentiment analysis, verbatim quotes with figurative-language flags, and open questions or hypotheses typed distinctly. - Use Case: After a Tagger pass has tagged a two-hour user interview, run this Skill to produce a Field Notes document in the client's Drive folder, with each theme linked to BigQuery finding rows a reviewer can approve in Stu. ## Quick Start Analyze the tagged transcript for conversation 1042 in the client dataset and write the field notes document to the client Drive folder.

Frequently Asked Questions about analyst-@SLUG@

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a user research interview transcript with AI?▼

Run this Skill after the Tagger pass has tagged the transcript. It surveys tag summaries, walks line ranges taking compact notes, verifies every quote against the source lines, and writes themes, sentiment, and field notes to a Google Doc.

How does the skill verify quotes against transcript lines?▼

It runs a verify-citations command that checks each quote against its cited line_id and exits with an error naming any mismatch. Every finding must pass this check before write_finding is called, since write_finding only validates that the line_id exists.

Can the analyst write findings directly to BigQuery?▼

The SQL tool is read-only with writeMode blocked, so the only write path is write_finding, which targets one table. Findings are always written as proposed and require human approval in Stu; there is no parameter to self-approve.

Why should I read lines_current instead of transcript_lines?▼

lines_current reflects human-reviewed corrections via COALESCE(cleaned_text, original_text), while transcript_lines.cleaned_text holds unreviewed AI output. Quoting the unreviewed text attributes corrected sentences to participants.

What are the limitations of single-interview analysis?▼

The Skill scopes strictly to one interview and cannot perform cross-transcript synthesis, which requires two or more interviews. Themes from one person are reported as observations, and implications must stay local to that participant.