google-grey-opslisted

Launch and run Google Ads via the API from a developer token + OAuth/service account — the googleops CLI (workspace, doctor, plan=validate_only, apply PAUSED, verify read-back, activate, bulk across customers under an MCC), gmcops for Merchant Center — plus grey-market survival: agency/MCC account supply, identity/payment infra, AdsBot/cloaking/review-layer filters, RSA/unicode/path tricks, selfie/BOV verification, geo isolation, no-cloak surfaces, ban replacement, enforcement tracks, failure forensics, MC cascade, per-vertical playbooks (gambling, finance/crypto, nutra, dating, loans, apps). Use for: 'launch Google ads through the API', 'I have a developer token / MCC, set up campaigns', 'bulk launch on N customer ids', 'PMax/Shopping/Search via script', 'why did the mutate fail', 'USER_PERMISSION_DENIED'. Clean buying theory = google-ads; feed spec/GMC launch = google-feed-ops; metrics = tracker-ops.
sergeyizmailov/knowledge-delta-skills · ★ 3 · AI & Automation · score 76

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

# Google Grey Ops Reviewed 2026-09-02. Baseline: Sonnet 5 / Claude Code subagent / 2026-09-02; 2026-09-03 blind cascade task [A] — payment+email cascade named only when prompted. Launch/operate via API on your own MCC credentials (`googleops`, `10`) + survive aggressive verticals without losing accounts, domains, payment identities. **`googleops`/`gmcops` are NOT yet live-verified** (2026-09-03): offline tests only, no run against a real customer. A human watches the first live `plan` → `apply`; record the result in `10`. ## Start here | You are… | Read | Then | |---|---|---| | In a directory with `workspace.json` | `references/10-googleops-agent-cli.md` | `googleops --workspace . --json …`; stop reading | | Handed a developer 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`), `doctor`, then `plan → apply → verify → activate` | | Setting up access (OAuth vs service account, MCC, refresh-token death) | `00` §1, `google-ads/10` §Access | back to `00` | | Merchant Center: gates, link, products | `google-feed-ops/04` + `gmcops` (`10`) | grey cascade rules in `12` | | Hit an error, a gate, a suspension | `00` § "When a step fails" | the one file it names | **Agent writes a JSON spec; `googleops` validates, creates PAUSED, reads back, activates.** Never hand-assemble a `MutateOperation` or call a mutate outside the CLI. New shape → extend `gads_spec`/`gad