AGENT SKILL

ad-account-auditor

Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分

License 许可
Apache-2.0
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
ad-account-auditor
slug
aaron-ad-account-auditor
class
auditor
license
Apache-2.0
summary
付费广告账户审计/ROAS评分
version
19.0.0
homepage
https://github.com/aaron-he-zhu/aaron-marketing-skills
metadata
{ "phase": "activate", "author": "aaron-he-zhu", "hermes": { "tags": [ "marketing", "ad", "activate" ], "category": "ad" }, "version": "19.0.0", "openclaw": { "emoji": "🎯", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills" }, "discipline": "ad", "geo-relevance": "medium" }
description
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
displayName
Ad Account Auditor · 付费广告账户审计
when_to_use
Use when checking whether a paid account or portfolio is safe to launch or scale. Requires normalized own-data outcomes, attribution windows, currency, conversion lag, and business constraints.
allowed-tools
WebFetch
argument-hint
<campaign + outcome exports> <currency/window/lag> [profile]
compatibility
Claude Code and compatible agent-skill hosts

02 资源文件 1

03 SKILL.md 正文

Ad Account Auditor

Audit one paid-media account or portfolio for incremental contribution and operating quality under declared constraints. Platform-reported ROAS is one input, never the objective or truth set by itself.

When This Must Trigger

  • Before launching, materially increasing spend, or changing a risky bid/targeting strategy.
  • When tracking, attribution inflation, unsafe placements, claims, or wasted spend are in doubt.
  • When the user requests a ROAS/RQS account audit from their exports.

Quick Start

Audit this USD account for direct response using 7-day click, 3-day lag, and $120 CAC ceiling.
Run the incremental-profit profile against the holdout and order-ID exports.

Skill Contract

Reads: one normalized account/portfolio evidence set. Writes: only a permissioned v3 artifact. Done when: required context and all 20 states are explicit, vetoes use verified evidence, and scorer output is reported without executing spend changes.

This skill judges. conversion-signal-qa, attribution-reconciler, campaign-architect, ad-creative-builder, and budget-pacing-monitor build/fix the inputs. Never enable campaigns, change bids, upload audiences, or scale budgets without separate explicit approval.

Data Sources

Need Preferred evidence
Delivery/spend Campaign, query, placement, audience, and change-history exports
Outcome truth Deduplicated order/lead IDs from ecommerce, analytics, or CRM
Economics Currency, margin/contribution, CAC/payback constraint
Attribution Platform + own-data timestamps/IDs, normalized windows and lag
Safety/claims Placement report, rendered ad/landing, approved claim/disclosure state from offer-claims-registry (the paid claims SSOT)
Incrementality Holdout/geo split/causal test, otherwise explicitly labeled proxy

Instructions

Runtime and Setup

Read ../../../references/auditor-runbook.md, scoring-semantics.md, roas-benchmark.md, and the ROAS catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable main. Before deterministic calls, follow runtime-invocation.md, resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}", and require the scorer, validator, and typed catalogs. If unavailable, return score_state: NOT_SCORED / score_confidence: not_scored with no gate verdict or persistent artifact.

Declare profile (direct-response|prospecting|incremental-profit), target, currency, attribution window, conversion lag, business constraint, goal, and observation date. If any required context is missing, return NEEDS_INPUT/UNDECIDED.

Evidence and Scoring

  1. Normalize currency, windows, IDs, lag, and portfolio scope before comparing metrics.
  2. Score all 20 R1..S5 criteria from the benchmark with source/date/type/confidence.
  3. Use Unknown for missing own-data truth, placement exports, or reconciliation. No data is not a veto and cannot be N/A merely because access is inconvenient.
  4. Verify vetoes:
    • ROAS-R1: instrumentation demonstrably fails the named own-data truth set.
    • ROAS-R2: material double-counting/inflation is demonstrated.
    • ROAS-O1: material claim/disclosure failure against the offer-claims-registry approved state.
    • ROAS-O2: applicable platform/restricted-category violation.
    • ROAS-A1: placement evidence demonstrates a material safety breach.
  5. Run the typed scorer. Report estimated/proxy incrementality as such; do not call platform attribution causal.

§2 ROAS Worked Examples

  • Complete direct-response profile, raw 78, no veto/fail: DONE/SHIP, final 78.
  • Complete profile, raw 78, one verified R1 failure: DONE_WITH_CONCERNS/FIX, final 59.
  • Complete profile, verified R1 and R2 failures: DONE/BLOCK, raw retained, no final score.
  • Missing placement report: A1 Unknown, NEEDS_INPUT/UNDECIDED, no overall score.

§3 ROAS Guardrails

  • High reported ROAS can reflect under-spend, branded-demand capture, or attribution inflation.
  • Learning-phase disruption is an S2 finding, not an automatic veto.
  • ATT/modeled data may reduce confidence; it does not automatically fail R1.
  • Frequency, creative fatigue, and audience saturation require separate evidence.
  • Never compare cross-platform returns before normalizing currency/window/lag and deduplicating outcomes.

§5 ROAS Translation

Lead with business impact and evidence. On trace request, qualify ROAS-R1/R2/O1/O2/A1; do not expose bare IDs that collide with RAMP/ECHO/TALE.

Report and Verdict

Begin with the auditor-runbook's exact typed conversation header. Never replace status, verdict, or score_state with prose; list each explicitly missing qualified item as ``ID: `unknown``` before findings.

Show verdict, profile/context, score or coverage/interval, confidence, R/O/A/S detail, reconciliation table, verified critical controls, Unknown evidence, and prioritized fix/owner/rerun condition. The scorer owns status/verdict and the 59 ceiling.

Validation Checkpoints

  • Scope/currency/window/lag/constraint/goal are explicit.
  • Own-data outcome truth is separated from platform self-report.
  • All 20 items have valid states and provenance; Unknown is not renormalized.
  • Veto failures are positively verified.
  • No spend/account mutation occurred without separate approval.

Persistence

Persist only after explicit authorization to memory/audits/ad/YYYY-MM-DD-<topic>.md. Assemble and validate the complete v3 draft with validate-audit-artifact.py against that intended --relative-path, persist only through one full-content Write, then revalidate the target as required by the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Do not autonomously write hot cache, claims, candidates, or account state.

Reference Materials

Next Best Skill

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6