AC webinar-warrior
Autonomous webinar strategy and content builder for coaches, course creators, community builders, and service providers. Use this skill immediately when the user asks to build a webinar, create a webinar strategy, write webinar emails, design a webinar offer, build a webinar funnel, write a webinar script, create a slide deck outline, or plan a product launch presentation. Also triggers for any conversation about selling from stage, live training strategy, converting an audience to buyers, building a high-ticket offer, or the phrases perfect webinar, webinar funnel, or live training. Built by Adrian Boysel at Brand Butler.
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 63/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
- 30Running it twice. 11 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2765 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 630: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 41 items
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.