transcript-fixer
Corrects speech-to-text errors in transcripts using AI and rule sets.
Install
mkdir -p .claude/skills/transcript-fixer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4280" && unzip -o skill.zip -d .claude/skills/transcript-fixer && rm skill.zipInstalls to .claude/skills/transcript-fixer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Corrects speech-to-text transcription errors using dictionary rules and AI-powered analysis. Builds personalized correction databases that learn from each fix, auto-loads person-name ASR variants from your people roster, and reads per-domain context files that prime the AI pass for context-dependent homophones. Triggers when working with ASR/STT output containing recognition errors, homophones, garbled technical terms, person-name errors, or Chinese/English mixed content. Also triggers on requests to clean up meeting notes, lecture transcripts, interview recordings, or any text produced by speech recognition. Use this skill even when the user just says "fix this transcript", "clean up these meeting notes", or mentions garbled names without invoking ASR specifically.Key capabilities
- →Apply dictionary-based transcription corrections
- →Build personalized correction databases
- →Extract uncertain ASR tokens for review
- →Load domain-specific correction presets
- →Generate diff reports for changes
How it works
It uses a two-phase pipeline: a deterministic dictionary filter for known errors followed by an AI-powered pass to resolve remaining context-dependent mistakes.
Inputs & outputs
When to use transcript-fixer
- →Fix errors in interview transcripts
- →Clean up meeting notes
- →Apply custom vocabulary corrections
About this skill
Transcript Fixer
Use the correction loop:
- Stage 1 applies deterministic, already-known corrections.
- Native AI Correction reads the complete transcript, fixes one-off errors, verifies uncertain entities, and compounds reusable fixes.
Native AI Correction is the default. Stage 1 alone is incomplete. Stage 3 API exists only for automation that has no Claude/Codex agent available.
Operating contract
- Finish Stage 1 → Native AI Correction → compound confirmed recurring fixes. Do not report a transcript clean after Stage 1 alone.
- Skip Native AI only when the human explicitly limits this run to the dictionary pass or a dated artifact proves Native AI already ran on this exact transcript.
- In Claude Code or Codex, do not run Stage 3. Use Stage 1 plus the native workflow.
- Never rewrite speech for fluency. A correction must explain a plausible ASR error and preserve who said what.
- A standard term elsewhere or a known participant is a candidate source, not proof of this occurrence's wording. Apply the occurrence-specific contrasts in Native review packets during the first pass and cold review; retain the raw form when the discriminator is missing.
- Before accepting a name-variant match, inspect the complete company/name slot; follow minimum occurrence checks. Ordinary wording refused by the name-shape guard uses only the bounded written-wording route, never a fabricated user/audio citation.
- By default, never infer or reassign speaker identities. Preserve speaker-label lines; human-confirmed labels and user verdicts are authoritative. Only an explicit, task-scoped user grant to infer identities opens the separate derived-reader branch: read scoped speaker inference before acting. That grant is permission to infer, not an identity confirmation or permission for other transcripts.
- Before correcting any person name, directly read both the configured global people roster and the owning project's explicit identity roster or alias ledger. Stage 1 auto-loads only global
ASR 变体entries; it does not load project rosters or expose suppressed, disabled, and unlisted entries. If an expected source is missing or the sources conflict, leave the name unchanged and enqueue or ask once. Never use occurrence frequency as identity evidence. Read references/dictionary_identity_and_context.md before settling the name. - Resolve doubts from available evidence before escalating. Audio download is one evidence channel, not a prerequisite for Native correction. When it is unavailable, follow evidence selection and escalation; do not require the user to change download permissions or treat every pending row as a question only they can answer.
- Leave genuinely unresolved text unchanged and enqueue it. A visible garble is safer than a fluent wrong guess; a pending row records uncertainty, not an automatic human handoff.
- When the user is unavailable or declines annotation, continue ordinary archival with unresolved wording retained and its quality recorded in metadata. Keep the queue/evidence in background storage; do not require a visible checklist or pretend the transcript is final. Ask only when a concrete downstream decision needs a missing discriminator the user possesses.
- Treat an unfamiliar token as unknown, not as an error. Exhaust the local evidence ladder first. For a load-bearing token that remains unresolved, use the clip-level cross-recognizer rung only when source audio and a permitted second engine are already available; otherwise continue with the available evidence under the escalation policy above. Agreement from a genuinely different recognizer family strongly corroborates the sound, but never chooses between homophonic spellings or overrides the person-name gate. Read native workflow step 4, rung 7 before using it. A backlog of exhausted pendings is the batch form of this rung: when a native pass leaves a queue of locally-unresolvable rows, do not hand the queue to the user wholesale — check it with
verify_queue_audio.py(one transcript, one source audio, one second engine, two clip windows per row). The script can attach acoustic evidence but never records a verdict; identical clips and readings that do not support the disputed word boundary remain pending for adjudication. The operator matrix and timestamp-mapping pitfalls live in advanced_correction_evidence.md § Batch pending adjudication. - Before correcting metadata, rerunning, or reversing an edit, follow metadata provenance for the protected audit boundary and ledger-writing contract.
- Read references/native_ai_full_workflow.md in full before performing a native pass. Contiguous, nonoverlapping reads may cover the full file; if a response is truncated, read the missing range before proceeding. An executed
catdoes not establish that its full output was received. Read the task-specific references named below before their corresponding action; use bounded, nontruncated reads for those files too.
Run context
Run every entrypoint through uv run; entrypoints that need third-party Python packages declare them with PEP 723, while stdlib/internal-only utilities may omit the metadata block. Execute commands from the skill directory printed when this skill was invoked, or prefix every script path with that directory. Do not rely on $CLAUDE_SKILL_DIR; it is not available in every harness.
If the bundle location is genuinely unknown, use the installation-resolution procedure in references/installation_setup.md. Do not select the first result from a broad find: caches, backups, and old versions can coexist.
For a clean document library, configure background intermediate storage. The persisted setting controls ordinary CLI defaults; it does not settle pending items.
To reuse versioned shared dictionaries, people rosters and domain contexts, configure the optional source reader and native publication binding. Unbound standalone behavior stays unchanged; shared names and context do not confirm speaker identities.
Quick start
Resolve <domain-context.md> through the context location
before filling the explicit file argument below.
# Initialize once
uv run scripts/fix_transcription.py --init
# Stage 1 for one project domain. --apply-domain trusts that explicitly
# selected, human-curated domain; occurrence ambiguity and context vetoes defer.
uv run scripts/fix_transcription.py \
--input meeting.md --stage 1 \
--domain myproject --apply-domain --json
# Several sibling domains may be loaded as one union.
uv run scripts/fix_transcription.py \
--input meeting.md --stage 1 \
--domain myproject,myproject-alt --apply-domain --json
# Preview without writing the Stage 1 output.
uv run scripts/fix_transcription.py \
--input meeting.md --stage 1 --domain myproject --dry-run
# Scan all documented context traps after the native read-through.
uv run scripts/fix_transcription.py --scan-traps \
--context-file "<domain-context.md>" \
--input meeting.md
Safe mode is the Stage 1 default: low-risk rules apply; medium/high-risk matches defer to *_needs_review.md and the persistent review queue. Applied: 0 is a valid result, not proof that the transcript is clean.
Stage 1 result contract
An unchanged-input Stage 1 result is:
{
"applied": 0,
"deferred": 0,
"output_path": null,
"needs_review_path": null,
"input_unchanged": true,
"review_enqueued": 0,
"stage1_only_incomplete": true,
"stage2_total_chunks": 0,
"stage2_failed_chunks": 0,
"stage2_degraded": false,
"boundary_refused": 0,
"boundary_check_active": true
}
Read every field in the result. boundary_refused counts dictionary matches the word-boundary check refused this run — neither applied nor deferred, so a caller comparing runs can see why a deferral disappeared; --apply-all switches that check off. When boundary_check_active=false, a zero refusal count does not establish that the check ran. stage1_only_incomplete is additive to the original caller contract and must remain true for a Stage 1 script run; only the caller can close it by running Native AI, or by explicitly choosing the agent-less Stage 2/3 route. The stage2_* telemetry fields are always present: Stage 1 reports 0, 0, and false; Stage 2/3 replace them with the actual API outcome. Do not infer no-op or success from whether a sidecar exists.
When a rerun auto-finalizes an earlier Stage 1 sidecar, applied=0 counts new corrections in this invocation while input_unchanged=false records the promotion. The result also carries stage1_publication: {"schema_version":1,"state":"already_promoted","canonical_path":"<absolute-input>","sha256":"<current-canonical-sha256>"}. Validate this complete object, require output_path to resolve to the same regular canonical file, and compare its current bytes with the supplied SHA-256 before continuing. Do not promote the canonical again or accept this state on a dry run, alongside new corrections/deferrals, or without a matching digest. Missing publication evidence does not relax the ordinary no-op/sidecar contract; stale bytes require a fresh result rather than an overwrite.
For a native end-to-end example, read [references/example_session_dji_minutes.md](references/example_session_dji_minutes
Content truncated.
When not to use it
- →Correcting non-ASR/STT generated text
- →Applying high-risk rules without review
Prerequisites
Limitations
- →Safe mode defers medium/high-risk rules to sidecar files
- →Audit function cannot definitively identify all false positives
How it compares
It maintains a persistent, learning correction database that improves accuracy over time, unlike manual find-and-replace methods.
Compared to similar skills
transcript-fixer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| transcript-fixer (this skill) | 1 | 4mo | Review | Intermediate |
| docs-write | 22 | 9mo | No flags | Beginner |
| content-research-writer | 15 | 1y | No flags | Beginner |
| doc-coauthoring | 16 | 11mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by daymade
View all by daymade →You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.