Skip to main content
The best way to run ads with an AI assistant is not a chat. It is a project: a persistent workspace where the agent already knows your business, your accounts, your rules, and your goals before you type a word. Claude Cowork, ChatGPT, Claude Code, and Codex Desktop all have one. The names differ; the shape is the same.
Not connected yet? Connect Adspirer in your client first — Claude Cowork, ChatGPT, Claude Code, Codex Desktop — then come back here. A project is where the connection lives; it is not a substitute for it.

​
Set it up in your client

Pick your client and follow the numbered steps. Each one puts the same five things in place: one project per ad platform, agent instructions, agent context, scheduled tasks, and agent skills. What each part is for is explained further down. For the folder-based clients (Claude Code Desktop, Claude Code Terminal, Codex Desktop) the whole install is one move: download the kit .zip from Expert Space, attach it to a chat, and send the install prompt. The agent unzips it, puts the skill where it loads skills from, checks that Adspirer is connected, and updates its own instructions and memory so every future session knows the expert exists. You never copy a file by hand.
Cowork has a dedicated field for every one of the five parts. Requires Claude Max, Team, or Enterprise, and the Adspirer plugin added from Customize → Plugins (Anthropic Directory) (setup).
1

Open Cowork

In the Claude desktop app (or claude.ai), click the Cowork tab at the top.
Claude desktop app with the Cowork tab selected

The Cowork tab in the Claude desktop app

2

Create one project per platform

Click + next to Projects in the left sidebar. Start from scratch or use an existing folder on your computer; pointing it at a folder that already holds your brand documents is the fastest route. Name it “Brand — Google Ads”.
3

Paste the agent instructions

Open the project’s Instructions panel and paste your instructions: the template below, or the kit’s AGENTS.md (the kit page’s Copy instructions button puts it on your clipboard). Every task and every scheduled run in the project inherits them.
4

Add context to the Context folder

Drop your business docs, exemplars, P&L summary, marketing docs, past-test log, and the kit’s references/account-profile.md into the project’s Context folder. Run /setup once and the plugin scans the folder, pulls live campaign data, and writes a brand context file alongside them. Leave Memory on.
5

Upload the skill

Click Customize in the left sidebar, open Skills, and upload the kit .zip as-is. It sits next to the skills the Adspirer plugin installed: those cover advertising in general, this one covers your account.
6

Confirm Adspirer and a notification channel

In Customize → Connectors, confirm Adspirer Ads & Performance Marketing Agent (the Anthropic-verified connector the plugin installs) shows connected, and link the ad accounts for this platform only. Set Interactive and Read-only tools to Always allow and leave Write/delete on Needs approval. Add Slack or email so scheduled runs can report.
7

Schedule the routines

In a chat inside the project, ask for the routine and Cowork offers to schedule it with /schedule. It appears in the Scheduled panel and runs remotely, laptop closed or not. Start with the weekly dashboard, read-only.
The full Cowork build, including the seven-property safety model for self-optimizing tasks, is in Cowork for Ad Ops.
Using Claude chat projects on claude.ai rather than Cowork? The pattern is identical: Set project instructions, upload context under project knowledge, upload the kit .zip under Customize → Skills. The playbook page walks through it.

​
What goes in a project

A well-built project has five parts. Get all five in place and the agent stops being a clever chatbot and starts behaving like a media buyer who has been on the account for a year.
Don’t want to write any of this yourself? The agent playbook from Expert Space is generated from your real ad account and ships every one of these parts as a file you upload into the right place. The rest of this page explains what each part is for, so you know where the files go and why.

​
1. One project per ad platform

Create one project for each ad platform you run. Google Ads gets a project. Meta gets a project. TikTok, LinkedIn, and Amazon each get a project. Which AI client you use doesn’t change this; it is the same rule in Claude Cowork, ChatGPT, Claude Code, and Codex. Why the boundary matters:
  • Each platform has its own rules. Google budgets are in dollars, Meta’s are in the ad account’s currency, TikTok rejects invalid objective and pixel combinations instead of correcting them. An agent scoped to one platform learns one rulebook and applies it correctly.
  • Account IDs never cross. The single worst ad-ops mistake is a change landing in the wrong account. A project pinned to one platform, with its account IDs written into the instructions, makes that structurally impossible.
  • Context stays relevant. Your Meta exemplars are noise in a Google Search project. Splitting by platform keeps every file in the project useful to every task.
  • Automation stays safe. Scheduled tasks inherit the project. One project per platform means one writer per portfolio, so two routines can never fight over the same campaigns.
Name projects so the platform is obvious from the sidebar: “Acme — Google Ads”, “Acme — Meta Ads”. Agencies add the client: “Acme — Google Ads”, “Bolt Coffee — Google Ads”. One project per client per platform is more projects, and that is the point. See managing multiple clients for the agency pattern in full. Inside each project, connect Adspirer and link only the ad accounts that belong there. Add a notification channel (Slack or email) if your client supports one, so scheduled runs have somewhere to report.

​
2. Agent instructions

Instructions are the agent’s constitution: read on every task, always on. They are the difference between an assistant that asks “which account?” every session and one that already knows. Write them in five short sections: Then set the agent’s default mode to how you actually work:
  • Builder — you hand it approved briefs and want campaigns built, verified, and monitored. Copy stays locked; it validates and reports, never rewrites.
  • Advisor — you want the portfolio truth and a recommendation. It analyzes and proposes, builds only when asked, and every budget call stays yours.
The rule that keeps instructions useful: rules go in instructions, data goes in context. Don’t paste your brand guide into the instructions field. Don’t put “never launch” in a document the agent might skip. Procedures and non-negotiables live here; everything the agent should read lives in the next part. For the full always-on version, with the standard operating loop and the interactive-versus-scheduled monitoring split, see Cowork for Ad Ops.

​
3. Agent context

Context is the data that makes the agent sharp. An agent with instructions but no context knows the rules and nothing about you. Give it what you’d give a senior hire in their first week. Keep the files short and current. A two-page brand summary beats a forty-page deck. Date anything that goes stale, and tell the agent in its instructions that live account data wins over any file.
A brand folder is the fastest way to give context. Claude Cowork, Claude Code, and Codex all work inside a folder on your computer. Put the documents above in it and the agent reads them; run /setup (Cowork, Claude Code) or ask Codex to set up the workspace, and the Adspirer plugin scans the folder, pulls live campaign data, and writes a context file for you.
Leave memory on where your client offers it. Project memory lets the agent carry naming decisions, prior builds, and your preferences across sessions, and it is scoped to the project so one platform’s memories never leak into another’s.

​
4. Scheduled tasks and routines

A project pays for itself when the agent runs without you. The same instructions, context, and skills, on a cadence, reporting to a channel you watch. This is what the agent can do automatically: Start every routine read-only. Let it propose for a few weeks, check its proposals against what you’d have done, and only then let it apply small, reversible changes with a per-run cap. A routine that changes budgets with nobody watching spends real money; the safety model for unattended changes covers shadow mode, change caps, single writer, and the kill switch. What each client calls it:
A Claude Code local routine only runs while the desktop app is open and your computer is awake. For anything that matters, pacing, spend spikes, disapprovals, create a remote routine instead. Cowork and ChatGPT scheduled tasks don’t have this problem.

A weekly dashboard routine. Paste it as a scheduled task in any client.

A small-changes routine with hard caps. Only after weeks of read-only runs.

Every scheduled run calls Adspirer tools again, so it draws on your monthly tool-call quota like a live conversation. Weekly is the right default for a review; daily is for accounts spending enough to justify it. The scheduled tasks guide has more example prompts and the late-run guardrails that keep a routine honest.

​
5. Agent skills

A skill is a step-by-step playbook for one job, loaded only when a task matches. Instructions say what the agent may do; a skill says exactly how to do it. That split is what lets you give the agent deep procedures without bloating every chat. Adspirer ships 13 free skills with every plan: the safety contract, the tool-call contract, one skill per platform, and cross-platform workflows for launching, reviewing, optimizing, and writing creative. They install with the Adspirer plugin in Cowork, Claude Code, and Codex, and ship inside the ChatGPT plugin. You never invoke them by name; describe the task and the agent picks the skill. Skills sit in a different place from instructions in every client: the Skills panel in Cowork and ChatGPT, a .claude/skills/ folder in Claude Code, .agents/skills/ in Codex. Keep them there. Don’t paste a skill into the instructions field, and don’t drop it into context as a document. Reference skills by name from instructions and scheduled-task prompts when you want to force one. The free skills know advertising. They don’t know your account. The agent playbook below adds a skill that does. Full reference: Agent Skills.

​
Where each part lives, by client

​
Skip the blank page: buy an agent playbook

You don’t have to write any of this from scratch. Adspirer generates an agent playbook for any ad account you’ve connected, built from that account’s real campaigns, spend history, and current state. It ships as a download containing every part of the project above, ready to upload into the right place.
1

Open Expert Space

Go to adspirer.ai/expert-space. You’ll see one card per connected ad account, grouped by platform, which is also why the one-project-per-platform rule fits it: one playbook covers one account.
2

Preview, then buy

Preview Expert shows sample prompts before you pay. Buy one account, or tick several and check out together. It’s a one-time purchase per account, and annual plans include one free; pricing and the bundle discount are on the playbook page.
3

Download the kit

The build takes a few minutes. From the kit page, click Download kit (.zip), or hit Copy instructions to put the agent instructions straight on your clipboard. Unzip it and you get one folder, named like google-ads-expert-<brand>/.
4

Upload each file into its part of the project

The kit is laid out to match this page. Use the table below.
What’s in the download, and where it goes:
The playbook follows the rule this page is built on without you thinking about it: AGENTS.md is rules, account-profile.md is data, SKILL.md is procedure, and they arrive as separate files so they land in separate places. The dossier is a dated snapshot; the agent is told live account data always wins, and rebuilding the kit against fresh data is free and unlimited from Refresh on the kit page.
The full install steps for every client, what each build stage does, and the FAQ are on the Prompt Engineering Playbook page.

​
Checklist

Before you call the project done:
  • One project per ad platform, named so the platform is obvious, with only that platform’s accounts linked
  • Instructions cover the business, the agent’s role, the north-star metric, the exact account IDs, and the golden rules
  • Context holds your brand guide, exemplars, margin data, marketing docs, and what has and hasn’t worked
  • Adspirer connected inside the project, with a notification channel for scheduled runs
  • Skills installed in the Skills panel or skills folder, not pasted into instructions
  • At least one read-only routine running: the weekly dashboard
  • Memory on
Then open a chat inside the project and ask:

The first prompt in any new project. The agent reads its instructions, context, and the live account, then tells you what it sees.

​
Where to go next

Scheduled tasks

More routine prompts, late-run guardrails, and what a cadence costs in tool calls.

Cowork for Ad Ops

The full always-on build and the safety model for routines that make changes.

Agent Skills

The 13 free skills, what each enforces, and how to install them per client.

Prompt Engineering Playbook

The agent playbook from Expert Space: instructions, dossier, skill, and prompt book generated from your account.

Managing multiple clients

One project per client per platform, without letting automation collide.

Connect your AI client

Cowork, ChatGPT, Claude Code, Codex Desktop, and every other client Adspirer supports.
Last modified on September 29, 2026