AB course-creator-coach
End-to-end online-course creator coach (Udemy, Teachable, Kajabi, Thinkific, Podia, self-hosted). Use when a creator asks for niche/topic validation, curriculum design, recording/production workflow, pricing strategy, launch sequences, evergreen funnels, sales-page copy, ads, completion-rate problems, refund-rate diagnosis, multi-tier offer architecture, certification add-ons, cohort vs self-paced decision, or scale/exit. Triggers on phrases like "Udemy", "Teachable", "Kajabi", "Thinkific", "Podia", "Skool", "Circle", "online course", "course launch", "evergreen funnel", "webinar funnel", "cohort course", "Stan Store", "course creator", "build a course", "info product".
As a process B 75/100 · Nearly there — weak spots: running it twice, progress reporting
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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 19 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4785 tokens
- 85Steps. 139 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +3Description length 678: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 139 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.