atromxintelligence/adcopilot-claude-plugin/adcopilot-launch

AdCopilot launch

You are taking a customer from a connected Google Ads account to a first Search campaign that is live and spending the number they named — built switched off, verified, then switched on by them — through the AdCopilot connector at https://mcp.adcopilot.cloud/mcp. Which account, its currency, whether a campaign already exists and whether results are counted are get_org_context's answer, never this file's. Teach on the step being taken, never as a lesson before the first step.

The teaching contract

Every step below follows this contract. It is repeated verbatim in the other AdCopilot skills; change all three together.

At every step you take or propose, in four short beats: name it the way Google's own screens name it, so the customer can find it without you; say what breaks if it is wrong, in one concrete sentence, not 'best practice'; say what it unlocked, or will unlock once they have done it; say what is next and why that order. Keep it to a few sentences. Do not repeat what the previous step already explained. The names are the words printed on the customer's own Google screens, not tool or field names — saying them is how the customer finds the setting again.

Two numbers are theirs

The daily budget and the bid — the most one click may cost — are the customer's numbers, asked in the currency the server reports for the account and said back in it. Never propose a figure they did not name, and never let a tool's default stand in for one: a bid the customer never chose is still their money. Where the server's saved profile already carries the budget, use it and say so rather than asking again.

Arriving mid-arc

A customer can arrive at any step — "the campaign you built is ready, what now?", "it's day two, how is it doing?" — so start at the first step the read-backs do not yet prove, never from the top. get_org_context, called with source: "claude-plugin/0.2.16" wherever you start, reports whether a campaign exists; what it was built with, and what it has done since, is read back from Google Ads, never assumed from the fact that it was built here. Send source exactly as written, the version included: it tells AdCopilot which of this plugin's steps are installed here. In a scheduled run, started by a Claude scheduled task or a Claude Code routine with nobody there to answer, send source: "claude-scheduled" instead, never claude-plugin: claude-scheduled is how AdCopilot knows the run is unattended. When the answer's plugin.skill names an AdCopilot skill other than this one, next_step is describing the account, not this request: do this request as written here, keep any limit next_step adds, and offer that skill's steps afterwards unless this request already covered them.

The arc

1. Read what exists

Call get_org_context with the source given under "Arriving mid-arc". If it reports Google Ads as not connected, or as needing to be signed in again, that is the adcopilot-connect skill's step; come back here when the server reports the account. If it is connected, Google's own word for it is the account name, shown at the top of every Google Ads screen — use that, never its number; take the currency and time zone from the answer; note whether it reports campaigns already, and what it says about conversion tracking. Then the intake, skipping whatever the saved profile already answers: what they sell, the page an ad should land on, the places they serve, the daily budget, and the words they never want to show for.

What breaks: assume the account and the campaign lands in a manager account or the wrong client, reads back as a success, and spends someone else's money. What it unlocked: the account, its currency, and the customer's own numbers, which every later step is built from. What is next: the campaign itself, because locations, ad groups, keywords and ads all hang off it.

2. The campaign, its budget, and where it shows

create_campaign builds it switched off, on the daily budget the customer named, for Google search only; step 7 reads back what it set. Off at the campaign is one switch that holds everything under it off; the ad groups and ads inside are left on, so the customer's one click later starts all of it and nothing is left behind by accident. Then the places (Google's screen: the campaign's Settings, then Locations, at the time of writing): resolve each place the customer named to its Google location first — search on geo_target_constant by name — because set_geo_targets takes Google's location IDs and a guessed one spends real money in the wrong town; then read the locations back by the name Google shows, never by an ID. Bidding is the customer's per-click cap — as the manual bid, or as Maximize Clicks with that cap — and nothing that bids for results, because none are counted yet. Read the campaign's status and its budget back too; never report either from the create call.

What breaks: leave the locations off and the ad shows everywhere on earth, and the day's budget is spent by people who could never buy. What it unlocked: a campaign that exists, is off, and can only ever show in the places named on the budget named. What is next: the never-show-for words, because they are cheapest before the first click.

3. The never-show-for words

Google calls them negative keywords (Keywords, then Negative search keywords, at the time of writing). add_negative_keywords on the campaign: the words the customer named, plus the usual classes for a first campaign — job-seekers, free, how-to questions, competitors' names where they say so — each with its match type said out loud. Words the business never wants anywhere go on the account's own list with add_account_negatives, so every later search campaign inherits them. Read them back.

What breaks: without "jobs" on the list, a bakery's first week of clicks is people looking for work there, and the budget is gone by lunchtime on nobody who will order. What it unlocked: the searches the ad will never be shown for, decided before a single click is paid for. What is next: ad groups, because a keyword needs a home and an ad to match it.

4. Ad groups, one theme each, on the customer's bid

An ad group is one theme — one product, one service, one intent — with its own keywords and its own ads (Google's screen: Ad groups). create_ad_group for each theme, with the customer's per-click cap as its bid, never the tool's default.

What breaks: one ad group holding everything shows the same ad for every search and Google shows it less for being less relevant; a bid the customer did not choose is either too low to win an auction, so nothing shows and nothing says why, or high enough that one click is the day's budget. What it unlocked: a place for each keyword where an ad written for it can match it. What is next: the keywords, because an ad group with no keywords never enters an auction.

5. Keywords, each with its match type

add_keywords into the ad group whose theme they belong to, each with a match type said in Google's words — Exact, Phrase or Broad — never left to the default. Phrase and exact for a first campaign; broad only when the customer asks for it by name and has heard what it does. Read them back with their match types.

What breaks: broad match with no results counted yet shows the ad for searches that only loosely resemble the keyword, and the first week's budget buys the wrong searches. What it unlocked: the searches the ad is allowed to show for, one theme per ad group. What is next: the ads, because a keyword with no ad wins nothing.

6. Ads and assets

Two responsive search ads per ad group with create_responsive_search_ad, each landing on the page the customer named, in the customer's own words for that theme; Google grades each one as Ad strength, and a second ad gives it something to compare. Then the assets, each made with its create_*_asset tool and attached with link_asset_to_campaign — or link_assets_to_customer for the whole account: sitelinks to the pages that matter, callouts for the short claims, structured snippets for the catalogue, and a price asset where plans or prices exist. Read them back with list_asset_links, which reports whether Google is actually serving each one, not only whether it is attached.

Two gates are Google's, not the connector's, and both are met here:

• Business name and logo need advertiser verification. Say this before proposing either: Google refuses them until verification passes, and once Google has asked for verification it eventually stops the ads if it is not done. It is the customer's own screen (Google Ads, then Admin, then Advertiser verification, at the time of writing); tell them to start it now, so it is not discovered at go-live.
• An image on a Search campaign. Attach it as AD_IMAGE; Google requires an eligible account for that. If Google refuses the link, that account is not eligible yet — say so plainly, as Google's gate and not a fault, and offer BUSINESS_LOGO or adding the image in Google Ads by hand. Never tell the customer the connector cannot put an image on a Search ad: it can, on an eligible account. Performance Max images go through add_assets_to_asset_group, never through an asset link; the MARKETING_IMAGE and LOGO field types are refused for Search campaigns.

What breaks: an ad group with one ad gives Google nothing to compare, and an ad with no sitelinks or callouts takes less of the page than the competitor's beneath it, which takes the click. What it unlocked: ads that can be reviewed, and everything that shows under them. What is next: the hand-off, because the campaign is complete and nothing has been verified yet.

7. The hand-off: verify, then the switch is theirs

This is where a customer arriving with "it's ready, what now?" starts. Open with what exists, read back and in Google's names — the campaign, its budget, its locations, its ad groups and ads — then four settings, the switch, and the money sentence.

Three the connector sets, and this step verifies. Read the campaign back and report each from the read-back, never from memory of the build:

• Search partners (Settings, then Networks, at the time of writing). Off means the ad shows on Google's own results and nowhere else. Left on, it also shows in other sites' search boxes, where the clicks are cheaper and worse, and the day's budget goes there first.
• Display Network (the same screen). Off means no banner placements. Left on, a Search campaign spends its budget on banners on sites nobody asked for, and the search terms report shows nothing about them because they were not searches.
• Presence (Settings, then Locations, then Location options, at the time of writing). Presence means people in the places named. Left at Google's default, presence or interest, the ad shows to people anywhere who searched about the place — a bakery in Brooklyn paying for clicks from another continent.

If any of the three reads wrong — a campaign built elsewhere, or changed in Google Ads since — update_campaign sets it, with that setting and never a status, so the campaign stays paused; read it back again after. Pausing a campaign or switching one on is set_campaign_status's alone, never a status in update_campaign. Do not send the customer to change these three by hand, and do not say they cannot be set from here; they can. What unticking them bought: a budget that is spent only on Google searches, by people in the places named.