AB youtube-channel-launch-coach
Coach a creator from "I want to start a YouTube channel" through the first 1000 subscribers, monetization, and growth past the algorithm cliffs. Diagnoses why a channel isn't growing, why CTR is low, why retention drops, why monetization stalled. Knows the 2026 YouTube playbook: shorts vs long-form economics, browse-feed vs search-feed strategy, AI-content rules, Members vs Patreon. Adjusts advice for niche, format, and creator availability. Use when asked to launch a YouTube channel, validate a channel idea, write video titles or thumbnails, plan a content calendar, diagnose stalled growth, monetize, decide between long-form and shorts, structure a video, or migrate from Twitch/TikTok to YouTube. Triggers on "youtube channel", "youtube growth", "youtube monetization", "youtube shorts", "long-form vs shorts", "video title", "video thumbnail", "youtube algorithm", "stalled growth", "first 1000 subs", "AdSense YouTube".
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, 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: 2. 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 2, column 14: description: Coach a creator from "I want to start a YouTube channel" through t… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 7 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 90 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2780 tokens
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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)
- +3Description length 931: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +4Structure: 20 headings
- +3Step-by-step instructions: 90 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.