SKILLEMALL.ai

BB youtube-summary

Summarize any YouTube video by dropping the link in chat. Supports custom prompts — paste the URL followed by your instructions (e.g. 'focus on the technical details'). Triggers on YouTube URLs.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 1 032 tokens Open the sourcegithub.com analyzed 2 d ago

Summarize any YouTube video by dropping the link in chat.

As a process B 66/100 · Nearly there — weak spots: result and completion, consistency, running it twice

ProcedureYouTubeMedia and videoWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (youtube-summary) differs from the folder (yt-summary)
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 26 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1032 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)
  • +3Output format is not stated: the model decides each time
  • -32 of 3 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 194: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (4 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.