AF youmind-youtube-transcript
Extract YouTube video transcripts and subtitles via YouMind API — no yt-dlp, no proxy, no local dependencies. Batch extract up to 5 videos at once with parallel processing. Saves videos to your YouMind board with timestamped transcripts in markdown. Works from any IP (cloud, VPS, CI/CD, corporate networks). Use when user wants to "get YouTube transcript", "extract video subtitles", "transcribe YouTube video", "batch transcribe videos", "get video captions", "summarize YouTube video", "YouTube 字幕", "YouTube 文字起こし", "YouTube 자막", or "download YouTube transcript".
As a process F 56/100 · Will not run — References files that are not bundled: ../../shared/PUBLISHING.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../shared/PUBLISHING.md - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 56/100
- 0Tools and files. 1 referenced file(s) missing: ../../shared/PUBLISHING.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 14 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 18 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2241 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (8 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -223 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +3Description length 567: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.