BB 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.
Transcribes audio or video to speaker-labeled, timestamped text, locally with MLX on Apple Silicon or remotely.
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 38. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 13963 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 729, 860, 1015, 1025): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 13963 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 82 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -2localhost URLs: will not work for another user
- -31 of 17 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 345: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 82 items
- +3Output format is stated explicitly
- +4Has examples (40 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.