BC youtube-manager
Comprehensive YouTube channel management with video publishing, data analytics, and report generation. Use when user mentions 'YouTube data', 'channel analysis', 'video statistics', 'monitor YouTube', 'YouTube reports', 'publish video', 'upload YouTube', or needs end-to-end YouTube workflow automation including video uploads, performance monitoring, and analytics reporting.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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-long-hermesdescription is 376 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (youtube-manager) differs from the folder (youtube-manager-smb)
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 47 steps
- 100Execution cost. Instruction body is 1060 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -33 of 3 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 376: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 47 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.