eval-transcription

Automates transcription quality evaluation by measuring WER, language accuracy, hallucination rate, latency against a baseline.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/euroconic/noter --skill eval-transcription
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-transcription
Source: https://github.com/euroconic/noter/tree/main/skills/eval-transcription
Command: npx skills add https://github.com/euroconic/noter --skill eval-transcription

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transcription quality in evolving systems can drift when models or pipelines change; this skill provides formal evaluation by measuring WER, language detection accuracy, hallucination rate, and latency against a baseline, preventing regressions from being shipped.

Core Features & Use Cases

  • Automated evaluation after changes to the transcription pipeline (daemon.py, model selection, post-processing, or audio input).
  • Baseline governance: store baseline metrics and enforce blocking thresholds to prevent regressions.
  • Multilingual evaluation and latency profiling across languages to guide model choices.

Quick Start

Run the eval after each change to the transcription pipeline to validate metrics against the baseline.

Frequently Asked Questions about eval-transcription

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

FAQPage Schema
How do I measure transcription quality after changing audio models?

Measure transcription quality by running an evaluation script to compute WER, hallucination rate, and latency against a stored baseline. This automated process detects regressions before changes are shipped to production.

What metrics are used for multilingual speech to text evaluation?

Multilingual speech to text evaluation metrics include Word Error Rate (WER), language detection accuracy, hallucination rate, and latency profiling. These metrics are compared against a baseline to validate model performance across different languages.

How do I prevent transcription regressions when updating post-processing pipelines?

Prevent transcription regressions by applying governance policies that block deployments or flag warnings when evaluation metrics fall below defined thresholds. Baseline metrics are stored to enforce these blocking rules automatically.

When should I run a transcription pipeline evaluation?

Run a transcription pipeline evaluation whenever changes affect daemon.py, model selection, post-processing logic, or audio capture. Evaluating after each modification ensures quality does not drift across real-world scenarios.

Do I need a specific dataset to evaluate audio transcription latency?

Yes, evaluating audio transcription latency requires a defined evaluation dataset and an eval/baseline.json file. These inputs provide the reference metrics needed to profile latency and compare performance against prior results.

What is the best way to automate hallucination rate detection in transcription?

Automate hallucination rate detection by integrating an evaluation script into your pipeline that computes metrics against a baseline dataset. This approach flags anomaly rates automatically whenever transcription models or processing logic change.