BC google-ads-account-settings-audit
Use for "audit my Google Ads settings", "is my account set up right", "I inherited this account, what's wrong with it", "why is my traffic showing outside my area", "check my campaign settings", "new client account review" — even when the user never says "settings". Covers search partners, Display expansion, location intent, auto-apply, ad rotation, conversion windows, budgets and bid strategies, each priced in the spend flowing through it. Most of these toggles default in Google's favour. Google Ads only.
Use for "audit my Google Ads settings", "is my account set up right", "I inherited this account, what's wrong with it", "why is my traffic showing outside 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. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3457 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 12 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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 511: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 20 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.