weekly-account-auditor
Skill2 starsChanged 4 months agoMITView on GitHub
Compare two complete Google Ads periods, explain the few changes that matter, and rank the next checks without changing the account. Use for a weekly review or when performance suddenly feels off.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run once a week with a current period and an equal comparison period.
- Distinctive: line 15
Use a connected Google Ads MCP, or paste exports with campaign metrics and date ranges.
- Distinctive: line 36
Do not turn hours of missing tracking into an estimated conversion count or "corrected" CPA.
- Distinctive: line 37
Do not invent revenue, profit, attribution, or a target the user did not provide.
- Distinctive: line 38
Never recommend a fixed percentage budget move from summary metrics alone.
- Distinctive: line 40
Search-term reports can omit low-activity queries.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Weekly Account Auditor
Doctrine
A useful account review explains movement, not just totals. Compare equal, complete periods in the account timezone, find the campaigns or ad groups driving the change, and put tracking gaps ahead of confident conclusions. Recent conversions may still arrive, so a bad-looking week is not final until conversion delay is accounted for.
When to use
- Run once a week with a current period and an equal comparison period.
- Use a connected Google Ads MCP, or paste exports with campaign metrics and date ranges.
- Bring the business target, primary conversion definition, currency, timezone, and known conversion delay when you have them.
Run it
Run a READ-ONLY weekly Google Ads audit. Use live account data if connected; otherwise use the exports I paste. Change nothing.
1. Confirm the account, currency, timezone, primary conversion, target CPA or ROAS, and two equal complete date ranges. If any are missing, mark the gap before interpreting performance.
2. Compare spend, impressions, clicks, conversions, conversion value, CPA, and ROAS only where the required inputs exist. Show the formula behind every calculated metric.
3. Find the campaign or ad-group drivers behind the largest useful changes. Use entity names and IDs, current value, comparison value, and absolute change.
4. Check conversion delay, tracking interruptions, partial days, and major account changes before calling a trend real. Never estimate missing conversions from the length of an outage.
5. Return at most 5 findings, ranked by business impact and confidence. Separate observed facts, likely explanations, and next checks.
End with a short action list labeled: investigate, keep watching, or ready for approval. Do not pause, scale, or edit anything. Say "No changes were made."Guardrails
- Equal complete periods only. Do not compare a partial day with a finished day.
- A tracking outage or unresolved conversion delay lowers confidence. It does not justify pausing campaigns or scaling winners.
- Do not turn hours of missing tracking into an estimated conversion count or "corrected" CPA. The missing number is unknown until it is reconciled.
- Do not invent revenue, profit, attribution, or a target the user did not provide.
- Never recommend a fixed percentage budget move from summary metrics alone.
- A low CPA does not prove a campaign has room to scale. Ask for impression share, budget limits, query coverage, and marginal performance before proposing more spend.
- Search-term reports can omit low-activity queries. State the coverage limit when search-term evidence is used.
Good output looks like
A five-minute review with the real movement, the entities driving it, the caveats that could change the verdict, and a short next-check list. No dashboard dump and no account changes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

