BC google-ads-performance-max-analysis
Use for "how is Performance Max doing", "is PMax cannibalising my Shopping campaigns", "I can't see anything inside PMax", "is Performance Max just buying my own brand traffic", "should I keep PMax or go back to Shopping", "what are my asset groups doing" — even when the user only says "PMax" or "my Google Ads black box". Also use when PMax conversions rose but the account total didn't. Google Ads only.
Use for "how is Performance Max doing", "is PMax cannibalising my Shopping campaigns", "I can't see anything inside PMax", "is Performance Max just buying my…
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 1. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3488 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 406: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 28 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.