tagger-@SLUG@

Applies a tag library to transcript lines and writes validated tags to BigQuery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Tagging research transcripts at scale is error-prone: untagged lines and never-read lines look identical, so partial tagging runs silently appear complete. This Skill separates judgement from bookkeeping — the model decides which tags each line earns, while a deterministic script serves batches, validates every tag against the active library, and proves the batches tiled the entire conversation. ## Core Features & Use Cases - Batch-driven tagging loop: A three-command cycle (next-batch, write-tags, status) serves 50-line ranges with surrounding context until coverage is complete. - Validated writes: Every tag is checked against the active tag library, per-tag confidence thresholds, batch line ranges, and non-empty justifications before any row is written to BigQuery. - Coverage proof: The status command derives completeness from recorded batch ranges and reports lines considered but untagged, distinguishing real zero-tag results from unread lines. - Use Case: After Scribe ingests a user-research interview transcript, run this Skill to apply the shared tag dictionary to every line, producing auditable tag rows with confidence scores and justifications. ## Quick Start Ask the agent to tag the latest ingested conversation by running the tagger batch loop until the status command reports complete coverage.

Frequently Asked Questions about tagger-@SLUG@

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

FAQPage Schema
How do I tag transcript lines in BigQuery with a tag library?▼

Run the tagger-batch script in a loop: call --next-batch to receive a line range with context and the active tag library, judge each line, then submit results via --write-tags with the batch range. Repeat until --next-batch returns done, then run --status for the coverage proof.

How does batch tagging prove full transcript coverage?▼

Each written batch is recorded in ingest_runs with its line range, and the status command checks that recorded ranges tile the conversation bounds with no gaps. Incomplete coverage exits with code 5 and lists the missing ranges.

Why was my tag payload rejected with exit code 3?▼

The whole payload is validated before any write: a tag is rejected if its tag_id is not active in the library, confidence is below that tag's threshold, the line_id is outside the served batch range, or the justification is empty. Fix the listed rows and resend the same range.

Can I write tags directly to the BigQuery tags table?▼

No. The script owns all writes to the tags table via a validated MERGE on line_id and tag_id. Direct inserts bypass threshold and range validation and would corrupt the coverage accounting recorded in ingest_runs.

What happens when a transcript batch earns no tags?▼

Send an empty tags array for that range. Recording a zero-tag batch is what advances the cursor, and the status report counts those lines as considered-but-untagged, which is a legitimate result distinct from lines never read.