CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asr-transcribe-to-text

Transcribes audio or video to speaker-labeled, timestamped text, locally with MLX on Apple Silicon or remotely. Use for 转录 / 录音转文字 / 说话人分离 / 字幕, and also for preparing audio for ASR without transcribing: 转格式, 降采样到 16kHz, merging recorder segments, or compressing and speeding up audio before 飞书妙记 — even when it looks like a one-line ffmpeg job.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Operationally excellent content: commands are copy-paste ready, the workflow is explicitly sequenced with validation gates and condition-bound recovery rules, and the reference bundle is real, well-signaled, and one level deep. The main weakness is token efficiency — heavy repetition (pyannote setup ×3, vLLM caps ×2) and long dated incident narratives that should be compressed or moved into the existing reference files.

Suggestions

State the pyannote one-time setup once (e.g., in the 'Speaker Diarization & Identification' section) and have the intro callout and Step 3 point to it instead of repeating the full instructions.

Move the Path B vLLM limits narrative (format/size/duration caps, offline cache, version notes) into a reference file like the other deep-dive topics, keeping only the symptom→cause Troubleshooting table inline.

Replace dated incident prose ('a 31-file batch died on file 11', '6 of 44 files in one batch', measurement dates) with the distilled rule plus a one-line pointer to the evidence, or collect the dated measurements in a dedicated evidence section.

DimensionReasoningScore

Conciseness

The ~1000-line body is noticeably verbose: the pyannote one-time setup is explained three times (intro callout, Step 3, and the Speaker Diarization section), the vLLM caps appear in full in Path B and again as a Troubleshooting table, and long incident-log prose ("a 31-file batch died on file 11", "6 of 44 files in one batch") plus inline time-sensitive measurements ("2026-09-19", "2026-07-16", "0.15.2rc1.dev68") pad sections that a competent agent could act on from a fraction of the text. It is not score-1 material — it never explains concepts Claude already knows — but several sections are padded well beyond the 'mostly efficient' anchor.

2 / 5

Actionability

Fully executable throughout: every route gives copy-paste-ready bash with all flags ("transcribe_long_whispercpp.py INPUT … --vad-model /absolute/path/to/ggml-silero-v6.2.0.bin"), expected output blocks, exact error payloads ("Audio exceeds maximum allowed duration of 600s"), and concrete decision tables mapping symptom to cause and fix.

5 / 5

Workflow Clarity

Steps 0–6 are clearly sequenced with route-selection rules up front, Step 4 is an explicit verification gate (non-empty output, anchored_ratio ≥ 0.5, checkpoint 'status: complete', preview to user), and batch/destructive operations have strong feedback loops — draft/admission boundaries, 'retry only when new input, preprocessing, parameters or evidence addresses the observed failure', and receipt-based completion that rejects 'N/N blocks complete' as a quality claim.

5 / 5

Progressive Disclosure

Good structure against the actual bundle: all 10 referenced files exist, are substantive, one level deep (they point back to SKILL.md rather than nesting further), and each inline link states what the file covers; scripts are catalogued in Bundled Resources. It falls short of 5 because sizable self-contained topics — the ~100-line vLLM limits narrative and the Feishu Minutes upload workflow — are fully inlined in SKILL.md rather than split into reference files like their siblings.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it answers what and when explicitly, packs several concrete capabilities into one sentence, and uses natural user-facing trigger phrases in both Chinese and technical vocabulary. The only gap is the absence of English trigger synonyms alongside the Chinese ones.

DimensionReasoningScore

Specificity

"Transcribes audio or video to speaker-labeled, timestamped text, locally with MLX on Apple Silicon or remotely" names the output format and execution modes, and the preprocessing half lists multiple concrete actions ("转格式, 降采样到 16kHz, merging recorder segments, or compressing and speeding up audio") — comprehensive coverage of the skill's domain in one sentence.

5 / 5

Completeness

Both halves are explicit: a clear "what" ("Transcribes audio or video to speaker-labeled, timestamped text" plus audio preparation without transcribing) and a concrete "when" ("Use for 转录 / 录音转文字 / 说话人分离 / 字幕 … even when it looks like a one-line ffmpeg job") — matching the anchor that answers what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural Chinese phrases users would actually say are well covered ("转录 / 录音转文字 / 说话人分离 / 字幕", "飞书妙记"), plus concrete technical triggers like "降采样到 16kHz". A few natural English equivalents ("transcribe", "subtitles", "speaker labels / diarization") are absent as explicit trigger terms, keeping it just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear ASR-transcription-with-diarization niche with distinct triggers (说话人分离, 飞书妙记, 16kHz downsampling, recorder segment merging); the explicit "even when it looks like a one-line ffmpeg job" clause stakes out the boundary against a generic ffmpeg/audio skill, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1039 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

daymade/claude-code-skills

Path

daymade-audio/asr-transcribe-to-text/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.