AC masterclass-builder
Create personalized multi-day masterclasses on any topic. Triggers on "teach me [topic]", "create a masterclass on [topic]", "I want to learn [topic]", "next lesson", "lesson [N]", "my courses", "course progress", or "resume [course]". Designs custom curricula, generates rich daily lessons with exercises, tracks progress, and adapts difficulty — like having a personal tutor who builds a course just for you.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (masterclass-builder) differs from the folder (normieclaw-masterclass-builder)
- 70When it triggers. States when to use, but not when not to
- 85Steps. 77 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 2882 tokens
- 100Progress reporting. Reports progress
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 410: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.