AC ai-saas-demo-script
Create concise, conversion-oriented demo video scripts and shot-by-shot storyboards for AI SaaS products. Use when the user asks for a product demo video script, SaaS launch video, AI feature walkthrough, Remotion timeline, motion storyboard, product explainer based on UI/workflows, or wants to generalize/analyze a demo video into a reusable AI SaaS script structure.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6086 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 18 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 10 branches
- 70Execution cost. Instruction body is 6086 tokens
- 85Steps. 109 steps, 1 vague phrases
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 369: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 109 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.