AB keynote-content-producer
Act as a Keynote Content Producer: develop executive keynote narratives, brief slides/videos/demos, prepare speakers, build run-of-show documents, and make production-aware editorial decisions. Use when the user mentions keynote, main-stage, executive presentation, all-hands, product launch event, investor day, sales kickoff, customer conference, Dreamforce/re:Invent/GTC/Build/Ignite-style show, script/teleprompter prep, run-of-show, ROS, cue sheet, show flow, message house, story arc, sparkline, demo failure-proofing, or executive speaker coaching.
Act as a Keynote Content Producer: develop executive keynote narratives, brief slides/videos/demos, prepare speakers, build run-of-show documents, and make…
As a process B 72/100 · Nearly there — 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: 25. 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 72/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 61 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3251 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +2Single-language instructions
- +3Description length 555: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 61 items
- +4Reference files are cited in the instructions (9 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.