AA run-paid-campaigns
Runs the paid leg of an approved plan: checks tracking, pages and stock before money moves, then stages one weekly proposal of kills, scales, pauses, swaps and launches, each with its reason and a check date. Nothing changes without your yes. Use when: launch these ads; it's Monday — kill, scale or pause?; swap this fatiguing ad; we sold out or the sale ended — pause the ads now; an ad got rejected or the account got restricted; we're in a brand crisis — hold the ads; give me the Google, TikTok or LinkedIn changes to make. Not for how the ads did or which ad won — use analyze-performance; not for rewriting a rejected image ad — use make-static-ads.
Runs the paid leg of an approved plan: checks tracking, pages and stock before money moves, then stages one weekly proposal of kills, scales, pauses, swaps…
As a process A 84/100 · Runs to the end — weak spots: running it twice
The same skill appears in 1 more place: goose-skills
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: 11. 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 84/100
- 30Running it twice. 11 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4357 tokens
- 85Steps. 43 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (16 tags): a typed call is more reliable
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 656: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 43 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (8 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.