google-grey-ops
Skill3 starsChanged 49 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sergeyizmailov/knowledge-delta-skillsword for word, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 1
- sergeyizmailov/knowledge-delta-skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- measurement-experimentation-opsSkill
- senior-buyer-opsSkill
- tracker-opsSkill
- deep-researchSkill
- knowledge-delta-skill-architectSkill
- web-scrapingSkill
- design-stack-pickerSkill
- normcore-webSkill
- responsive-adapterSkill
- google-adsSkill
- google-feed-opsSkill
- meta-adsSkill
- meta-grey-opsSkill
- js-obfuscationSkill
- secure-codingSkill
- tiktok-adsSkill
- tiktok-opsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Never hand-assemble a MutateOperation or call a mutate outside the CLI.
- Distinctive: line 66
Sequence payment events deliberately: No card add, method change, or threshold charge from an inconsistent context.
- Distinctive: line 140
Do not skip to remediation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/gads_build/gads_verify and test_googleops.py.
Boundary: "buy well" → google-ads · "don't get killed / source accounts / scale" → here ·
"feed and Merchant Center" → google-feed-ops · "count and sync" → tracker-ops ·
"portfolio and TL decisions" → senior-buyer-ops.
Authority: this skill governs grey-vertical execution; google-ads clean-marketing guardrails govern
compliant accounts. Route by lane; do not merge the two normative stances.
The Google model is not the Facebook model
Discipline transfers from meta-grey-ops; the risk map does not. They differ:
| Trust anchors on | Billing history — a disclosed, literal threshold ramp | Behavioral/social signals |
| Highest-risk moment | A payment event | A login |
Full 7-row comparison (destination review, cascade scope, burn radius, moderation timing, appeal
posture) → references/04-failure-forensics.md.
On Facebook you protect the session. On Google you protect the billing identity and the destination. Porting the Facebook playbook wholesale over-invests session hygiene, under-invests payment consistency and landing-page integrity.
Non-negotiables
- Classify the enforcement track first. Egregious (no warning, permanent, propagates) ·
non-egregious (mandatory 7-day warning) · Limited Ad Serving (throttle, not suspension). Most
costly error: treating recoverable as terminal or vice versa. See
04. - Know which replacement you are doing. New Google identity after your suspension =
Circumventing-systems violation, separately charged, propagates. Reseller swapping the seat
(their MCC, their invoice) is a different product — still cascade-risk if GTM, domain, phone, or
payment profile overlap. See
05. - Never submit false information during verification. Failing honestly pauses the account; lying
suspends it permanently — fabrication is never lower-risk. Org path skips the selfie; grey
self-reg does not pass BOV —
06. - Never chargeback. Named account-level suspension trigger; burns the payment method's future usability.
- Sequence payment events deliberately. No card add, method change, or threshold charge from an inconsistent context.
- Rotate on signals, not a timer; change one variable at a time — else the next burn is unattributable.
- Know whose MCC you are in. Cascade takes every account sharing it. Reseller who can't name the MCC owner = unknown compliance history inherited.
Route references
| Need | Reference |
| Account supply market, account types, linking signals, antidetect/proxies, compliant alternatives | references/01-account-supply-and-identity.md |
| Payment mechanics, threshold billing, invoicing eligibility, verification, virtual-card vendors | references/02-payments-and-billing.md |
| AdsBot official behavior, ValueTrack chains, Keitaro/RedTrack measurement config, domains | references/03-domains-trackers-review.md |
| Enforcement tracks, death modes, appeals under fire, scaling posture, Google vs Facebook | references/04-failure-forensics.md |
| Review-layer filters, cloaking stacks, white pages, RSA/unicode/path tricks, replacement | references/05-review-layer-and-cloaking.md |
| Advertiser verification, video selfie, BOV — live vs dead pass paths | references/06-verification-selfie-bov.md |
| Geo isolation: OFAC vs RU pause, tz/currency locks, billing vs serve | references/07-geo-isolation.md |
| Demand Gen sensitive inventory, App campaigns (no cloak), adult/CBD no-path table | references/08-surfaces-and-no-path.md |
API errors → survival response (freeze/replace/rotate); canonical code→fix in google-ads/11 | references/09-api-errors-grey-response.md |
| Ordered API launch path — START HERE for any launch | references/00-launch-runbook.md |
googleops / gmcops contract: commands, spec→API mapping, failure contract, offline checks | references/10-googleops-agent-cli.md |
| Autolaunch parity: why no Dolphin/FBTool for Google, farming tooling, aged-account market | references/11-autolaunch-parity.md |
| Merchant Center grey lane: MC↔Ads cascade, second-account trap, no Shopping cloak, dropship triggers, appeals | references/12-merchant-center-grey-lane.md |
| Per-vertical playbooks | playbooks/ |
Scripts
googleops is the agent write boundary (from this folder: uv tool install ., or prefix
uv run --project .). Workspaces inside the skill store are rejected; state lives in the project's
.googleops/.
| Script | Does | Spends? |
googleops.py | workspace/doctor → hash-bound plan (validate_only) → apply PAUSED → verify → explicit activate; bulk-plan/apply/activate; report/monitor/link | only activate/bulk-activate with --confirm SPEND |
gmcops.py | Merchant Center doctor (gates, programs, issues, link, product counts), products insert/status, API data sources, homepage claim, ToS, propose Ads link | no spend |
gads_spec.py · gads_build.py · gads_verify.py · gads_client.py · gads_workspace.py | implementation: spec rules, mutate graph, GAQL read-back, client/env, workspace | — |
test_googleops.py | offline tests (no network) | — |
Env: GADS_DEVELOPER_TOKEN + (GADS_CLIENT_ID/GADS_CLIENT_SECRET/GADS_REFRESH_TOKEN or
GADS_JSON_KEY_FILE), GADS_PROXY or GADS_ALLOW_NO_PROXY=1; GMC_JSON_KEY_FILE or
GMC_REFRESH_TOKEN for gmcops. Never pass a credential on argv.
Policy taxonomy, certifications, and the full appeal process live in google-ads/09 — read it before
any regulated vertical.
New-job bootstrap
- Collect access — MCC/account IDs, billing arrangement + owner, Merchant Center, tracker campaign URL, domains, proxy. Into gitignored project notes, verbatim.
- Establish the enforcement baseline — policy status, active strikes, verification state, Limited Ad Serving status (needed to diagnose later changes).
- Confirm certification requirements per target geo (
google-ads/09) before building. Gambling and financial services changed multiple times in 2026. - Wire tracking before spend. Tracking template with
{lpurl}/{gclid}, tracker campaign mapping; check whether the developer token can still onboard offline conversion import at all (2026-06-15 cutoff,google-ads/06). - Naming before first launch. Campaign name must encode whatever the tracker splits on; mapping
is not automatic (
tracker-ops). - Launch through
googleops(00): doctor → plan (validate_only) → apply PAUSED → verify → activate. - Review layer. Final URL = the white, same registrable domain, cloak off until serving. No
PMax cloak. No App-campaign cloak (
08). Filter stack in05. Confirm tz/currency and OFAC vs serve-geo (07) before first spend. - Agree kill rules in writing with the TL: spend-without-conversion cap, CPA cap, account verdict threshold, who decides on a ban wave.
Diagnose a failure in order
which track (A/B/C) -> account-level or item-level -> payment/verification or policy/content
-> domain-specific or account-wide -> then actDo not skip to remediation. A domain rotation on an account-level signal problem wastes a domain and teaches nothing.
Guardrails
- Redirects are not the violation. Content that differs conditioned on who is requesting it is —
that's Circumventing systems (no warning, permanent, cascade). Filter stacks/same-domain whites
(
05) don't make the track non-egregious. - Compromised site = disapproval tier. Malicious software = egregious. Not the same death sentence.
- "Temporarily paused" ≠ "suspended". Verification pauses recover by completing the task.
- Multiple accounts per business are not banned; the violation is the evasion pattern, not the count.
- Vendor pricing, spend ceilings, appeal-success claims in these files are vendor-reported, no published methodology — treat every number as a prior, not fact.
- Where a compliant path reaches the same goal, say so —
01maps each grey practice to its legitimate alternative; several are cheaper long-term (trust accrues to you, unrevocable by a third party).
Output
Lead with the track classification and whether the state is recoverable. Give the exact next action, the review timeline to expect, what to observe before the next change, and what single variable is being changed so the result stays attributable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

