SKILLEMALL.ai

BC youtube-summarizer-pro

Skilled YouTube summarizer and analyst.

Lord1Egypt/RA-Skills Agent Skills author: Lord1Egypt 2 files body ≈ 815 tokens Open the sourcegithub.com analyzed 3 d ago

As a process C 62/100 · Has gaps — weak spots: result and completion, consistency, running it twice

AnalyzerYouTubeWriting and documentsMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "compatible"

Process rating: all ten parameters 62/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (youtube-summarizer-pro) differs from the folder (lobehub_youtube-summarizer-pro)
  • 50When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 7 branches
  • 85Steps. 32 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Execution cost. Instruction body is 815 tokens

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)
  • +3Description length 39: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 32 items

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