meta-grey-opslisted

Launch and run Meta (FB/IG) ads via the workspace-bound Marketing API CLI (metaops): access/scopes/System User, MCP vs API, PAUSED bulk launch across ad accounts, edit/clone/rules, catalog/DLO/carousel creatives, catalog as an agent-edited Google Sheet, attribution 1/1/1, Advantage+ and multi-advertiser opt-out, EU DSA, BM setup (accounts/pixel/CAPI/users), review/monitor/comments, plus grey-market survival: antidetect/proxy/session hygiene, agency accounts, token death, cloaking/review-layer tricks, verification gates, no-path verticals, per-vertical playbooks (casino, nutra, crypto, news-tg). Use for: 'launch FB ads through the API', 'I have a BM access token, set up campaigns', 'bulk launch on N accounts', 'connect Claude to Meta ads / MCP', 'why did the ad set create fail', 'duplicate campaigns / set kill rules / hide comments via API'. Clean marketing theory = meta-ads; tracker metrics = tracker-ops.
sergeyizmailov/knowledge-delta-skills · ★ 3 · AI & Automation · score 76

Install: claude install-skill sergeyizmailov/knowledge-delta-skills

# Meta Grey Ops Reviewed 2026-09-03. Baseline 2026-09-03 (Sonnet 5 blind): bulk-launch task [K] — shared BM pixel still needs per-account attach (1815045). Launch/operate via API on your own token (= autolaunch SaaS without UI, `13`) + grey survival. "buy well" → `meta-ads` · "count & sync" → `tracker-ops` · "portfolio decisions" → `senior-buyer-ops`. ## Start here | You are… | Read | Then | |---|---|---| | In a directory with `workspace.json` | `references/16-metaops-agent-cli.md` | use `metaops --workspace … --json`; before activation also read `00` §6–8 | | Handed a token / asked to launch anything via API | `references/00-launch-runbook.md` | create a workspace in a project dir outside the skill (`scripts/specs/example-workspace.json`), validate it, then use `metaops` | | Setting up access, deciding MCP vs API, minting/handing over a token | `references/02-access-tokens-and-mcp.md` | come back to `00` | | Hit an error, a gate, a rejection, a dead token | `00` § "When a step fails" | the one file it names | **Agent writes a JSON spec; `metaops` controls the lifecycle; `launch.py` writes Graph payloads.** Never hand-assemble a payload or invoke a low-level Graph mutation directly. New shape → extend `metaops`/the implementation and its tests. ## Launch defaults (what every ad set/ad gets unless the spec says otherwise) | Setting | Default | Enforced by | Override | |---|---|---|---| | Object status at create | `PAUSED`, all levels | internal launcher; spend only via `