scribe-@SLUG@

Ingests interview transcripts from Google Drive into BigQuery via a deterministic script.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? LLM agents that walk a transcript document by hand and write rows themselves silently fail: they narrate an ingest that never happened, mangle long Drive ids, and report success with zero rows written. This Skill removes that failure by delegating all reading, parsing, and writing to a deterministic ingest tool, leaving the agent to judge dictionary corrections and report verified results. ## Core Features & Use Cases - Deterministic transcript ingest: Runs the scribe-ingest tool against a Google Doc transcript, writing conversations, participants, and transcript_lines into BigQuery with resumable cursors and verified outcomes. - Folder planning: Runs the tool in plan mode to list which documents in a client's Drive folder still need ingesting, resuming, or re-processing after edits. - Dictionary-based corrections: Scores correction candidates against active project_dictionary terms and applies approved fixes to transcript_lines, while never touching human-made edits in line_edits. - Use Case: Claire asks what transcripts remain for a client; you run the plan command, dispatch ingests per document, apply high-confidence corrections, and report outcomes, warnings, and human-edit conflicts verbatim from the tool's JSON. ## Quick Start Ask the agent to ingest the named interview transcript from the client's Drive folder into BigQuery and report the outcome, line count, and any warnings.

Frequently Asked Questions about scribe-@SLUG@

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

FAQPage Schema
How do I ingest an interview transcript into BigQuery?▼

Run the scribe-ingest tool with the client slug, dataset, channel id, and the document name. The tool resolves the Drive folder and credentials from the client's fence config, parses the transcript, and writes rows to conversations, participants, and transcript_lines.

How do I check which transcripts still need ingesting?▼

Run the same tool with the --plan flag instead of a document name. It compares the Drive folder listing against the conversations table and returns a JSON work list of documents to ingest, resume, or reprocess, which you return verbatim.

Can I retry a failed transcript ingest safely?▼

Yes, retries are safe by construction: ids derive from the source, writes are MERGE statements, and a cursor records what already landed. Re-running the same command resumes from the cursor so only the failed chunk is redone, except after exit code 5 verification failures.

Why must corrections never write cleaned_text equal to original_text?▼

A no-op correction corrupts downstream reads, which use COALESCE(cleaned_text, original_text). The previous pipeline produced 41% no-op corrections, so the rule is enforced: leave cleaned_text NULL when nothing changes and always set correction_type with any correction.

What are the limitations of LLM-driven transcript ingestion?▼

Measured testing showed a chat model walking the document wrote zero rows across eleven trials while reporting success each time, because long exact strings degrade under context pressure. That is why parsing and writing live in a deterministic script and the model only judges corrections.