daily-auditor
Skill3 starsChanged 5 months agoMITView on GitHub
The read-only morning audit: last 7 complete days vs the prior 7, wasted budget, fading ads, starved tests, pixel problems, one next test. Max 5 recommendations, changes nothing. Use every morning, or right now on any account you suspect is leaking.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- riz1k9/claude-ad-skillstheir own version, first seen Aug 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- riz1k9/claude-ad-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- angle-writerSkill
- audience-builderSkill
- brand-readerSkill
- budget-pacerSkill
- buyer-language-minerSkill
- catalog-commerceSkill
- competitor-ad-teardownSkill
- copy-formulasSkill
- creative-directorSkill
- fatigue-detectorSkill
- lead-gen-builderSkill
- media-buyerSkill
- pain-to-promiseSkill
- performance-analystSkill
- pixel-conversionsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 12
Every morning, same time, whether things feel fine or not.
- Distinctive: line 31
Read-only is the identity of this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Daily Auditor
Doctrine
Nobody looks at your ad account every day. Not the agency (check the activity history), not Meta (its recommendations optimize Meta's revenue), usually not even you. Meanwhile the best community advice is "stop touching your campaigns", which only works if something is still watching. The resolution: read daily, act rarely. A read-only audit is what lets you keep your hands off without flying blind.
When to use
- Every morning, same time, whether things feel fine or not. Quiet failures are the expensive ones.
- Also: on any account managed by someone else, as an accountability check.
- Needs a Meta Ads MCP, read access only.
Run it
Run a READ-ONLY audit of my ad account. Change nothing. Compare the last 7 complete days against the prior 7, at campaign, ad set, and ad level, and give me at most 5 findings, ranked by dollars at stake:
1. Wasted budget: spend with zero results, and where it is pooling.
2. Fading ads: flag ONLY if frequency > 4.0 AND CTR is down 30%+ vs the prior window. Name the ad.
3. Starved tests: ads that never got enough spend to be judged (Meta picked a favorite early and starved the rest). Tell me which ads never got a real test.
4. Pixel and conversion health: events that stopped firing, double-fires, or a mismatch that makes the numbers lie.
5. The one next test worth running, based on what the winners share.
For every finding: the numbers behind it, from the account. If a number is not in the account, say "no data", never estimate. If nothing is wrong in a category, say so in one line. End with: "No changes were made."Guardrails
- Read-only is the identity of this skill. It proposes; a human disposes.
- Max 5 findings. A 50-row dashboard dump is not an audit, it is homework.
- Week-over-week complete days only: partial days and lifetime views both lie.
- The fatigue rule (frequency > 4.0 AND CTR -30%) is a deliberate two-condition heuristic to avoid false alarms. It is falsifiable; if your data disagrees, tighten or loosen it and write down why.
Good output looks like
Five bullets you can read before coffee, each with real account numbers, ending in "No changes were made."
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.

