AF growth-experiment-backlog
Build and prioritise a growth experiment backlog. Use when asked to plan growth experiments, prioritise growth ideas, set up a test backlog, or run a growth process/sprint. Produces a prioritised backlog — each experiment as a hypothesis with the metric it moves, an ICE/PXL score, the minimum test design, and a definition of done; plus the cadence to run it.
Build and prioritise a growth experiment backlog.
As a process F 60/100 · Will not run — References files that are not bundled: ../marketing-funnel-plan/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../marketing-funnel-plan/SKILL.md
Process rating: all ten parameters 60/100
- 0Tools and files. 1 referenced file(s) missing: ../marketing-funnel-plan/SKILL.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 732 tokens
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 360: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.