lexicon-@SLUG@

Proposes and serves canonical dictionary terms with evidence from project transcripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research interview transcripts contain inconsistent spellings, misheard proper nouns, and undefined jargon that corrupt downstream correction and analysis. This Skill bootstraps and maintains a project dictionary in BigQuery so every future transcript is corrected against human-approved canonical terms. ## Core Features & Use Cases - Dictionary Bootstrapping: Builds the initial project dictionary from the first transcript, then reminds the orchestrator to re-run correction on that transcript once terms are approved. - Term Proposal with Evidence: Proposes clarification entries (term plus definition) and unification entries (one canonical term with variant spellings), each backed by quoted evidence lines and a calibrated confidence score. - Human-Gated Approval: Writes only proposed rows and never sets active status, ensuring a human decides before any term enters the dictionary. - Dictionary Serving: Returns only active terms to other agents such as Scribe and Tagger, never leaking unapproved proposals. - Use Case: After ingesting the first client interview, the agent proposes canonical forms like Acme Corp with variants ACME, Acme, and A.C.M.E., each with transcript quotes, so a human can approve them and future transcripts are auto-corrected. ## Quick Start Ask the agent to scan the first ingested transcript and propose canonical dictionary terms with evidence for human review.

Frequently Asked Questions about lexicon-@SLUG@

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

FAQPage Schema
How do I build a project dictionary from interview transcripts?▼

Ingest the first transcript conservatively with no dictionary correction, then have the agent propose canonical terms with quoted evidence. A human approves or rejects each proposal, and the transcript is re-corrected against the approved dictionary.

How do I unify inconsistent spellings of names in transcripts?▼

Create a unification entry with one canonical term and all surface variants in a variants array, such as Acme Corp covering ACME, Acme, and A.C.M.E. This lets the correction agent fix mishearings across the corpus.

Can the lexicon agent approve its own dictionary proposals?▼

No. The agent is structurally forbidden from setting status to active and can only write proposed rows. A human makes the approval decision, which prevents a single bad entry from poisoning all future transcript corrections.

What evidence is required for a dictionary term proposal?▼

Every proposal must include an evidence array of conversation ID, line ID, and quote pointing to the transcript lines that establish the term. Proposals without evidence are dropped, and confidence scores reflect how explicitly the transcript defines the term.

Why is the first transcript re-corrected after dictionary approval?▼

The first transcript is ingested before any dictionary exists, so it remains the worst-corrected interview in the corpus. Re-running correction against the newly approved dictionary brings it up to the same standard as later transcripts.