AB video-no-subtitle-transcribe
Fallback transcription for videos without subtitles. When a video (YouTube/Bilibili, etc.) has no subtitles, subtitle endpoints are disabled or fail, download audio with yt-dlp and transcribe locally with faster-whisper, outputting a full timestamped transcript. Triggers: no subtitles, transcribe video, subtitles disabled, whisper transcription, extract speech.
Fallback transcription for videos without subtitles.
As a process B 75/100 · Nearly there — weak spots: running it twice
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 4, column 14: description: Fallback transcription for videos without subtitles. When a video … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 75/100
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 27 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1176 tokens
- 100Progress reporting. Reports progress
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
- +2Single-language instructions
- +3Description length 363: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.