Meta Ads audit: measurement, Pixel, CAPI, creative and policy

Prerequisites: a Meta Ads (Facebook/Instagram) account with ad spend to audit — advertising on Meta is billed; access to your Pixel, Events Manager and conversion data; nothing else — the skill is an audit methodology, it does not place or manage ads itself Install "Meta Ads audit: measurement, Pixel, CAPI, creative and policy" for me. It gives the agent @agricidaniel's Meta Ads audit procedure from the claude-ads toolkit: collect objective, conversion definition, geography, date window, timezone, currency, spend and data sources; evaluate Pixel and Conversions API health, attribution windows and conversion lag, creative diversity and fatigue, account structure, audiences, placements, automation, budgets and policy exposure; separate observations, diagnoses, recommendations, opportunities and proposed mutations; mark uncertainty and contradictions; keep every account change as a draft until the mutation gate passes — with the cold-start evidence contract that classifies account/Pixel/conversion maturity independently. MIT-licensed (declared in the source repo). Repository: https://github.com/agricidaniel/claude-ads/blob/main/skills/ads-meta/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "ads-meta". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing to install yet — grant the agent access to your Meta Ads account exports, Pixel and Events Manager data when you want an audit). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.