google-ads-setup

Google Ads — Setup

You build account-context.yaml, the single source of business truth that every other skill in this suite reads. Nothing downstream (audit, plan, builder, pusher, tracker, optimizer) runs without it.

Operating rules

• Establish ONE working folder per business and keep everything in it — see ${CLAUDE_PLUGIN_ROOT}/references/workspace-layout.md. On first run, agree the <workdir> path with the user, create it, and write account-context.yaml there. Every downstream output goes into its dated subfolder (audits/, plans/, builds/, changes/, raw/). NEVER scatter files into the plugin folder, D:\tmp, /tmp, or the cwd root — a user who installs the plugin must get ONE tidy folder, not sprinkled files.
• Secrets are POINTERS, never copies. Do NOT write raw API tokens/keys into the working folder, any output, or account-context.yaml. The connections registry records where each token lives (via: env:/path#KEY, via: server:/path, via: mcp:<id>) and it's read at runtime. If the user wants creds kept locally, a gitignored secrets/ in the workdir — never committed, never in a report.
• (legacy) Write account-context.yaml to the working directory, NEVER inside the plugin folder. Business data lives with the user, not in the code. (Use --context <path> if the user names one.)
• Detect by capability, not by hardcoded server ids. Inspect the connected MCP tools and match them to roles. The same skill must work for any user's MCP setup.
• Setup is the CONNECTION HUB. Its job is to inventory EVERY data source the suite needs and consolidate how to reach each one into the context's connections block — ONE place every downstream skill reads, so no skill ever re-discovers a connector or silently runs without data.
• NO-FABRICATE DATA GATE (non-negotiable, the whole point). Missing data is connected or flagged, NEVER invented. If a source is missing: (a) guide the user to connect or provide it (concrete steps — link the account, point to a .env/secrets file, a data-hub script), and (b) if it stays missing, record it as MISSING in connections so every downstream skill that needs it labels that part of its output UNVERIFIED — connect <source> and EXCLUDES it from any number it reports. Skip-then-guess produces wrong analysis; an honest gap is correct. A blank field is honest; a fabricated AOV / store-revenue / feed status is dangerous.
• Confirm before writing. Show the assembled context, get a yes, then write.