mainbranch: Skill for Claude Code

.claude/playbooks/google-ads-search-launch/SKILL.md

google-ads-search-launch is a skill for Claude Code from noontide-co/mainbranch. It costs 43 tokens per session (1,928 once invoked), scanned A, original, MIT.

A reusable manual playbook for testing one offer with a tightly scoped Google Ads Search campaign and a landing page. Google Ads Search shows paid results when people search for related terms.

In plain words
What is it for?
Use it to plan one paid-search proof run aimed at leads, calls, bookings, deposits, trials, or another stated business outcome.
Why use it?
It defines the test, approval gates, conversion path, review window, and evidence without pretending to automate advertising accounts.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is noontide-co/mainbranch's own configuration. It tells Claude Code how to work on mainbranch itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mainbranch configures →

Part of the mainbranch plugin — 21 skills shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to noontide-co/mainbranch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/noontide-co/mainbranch/main/.claude/playbooks/google-ads-search-launch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/noontide-co/mainbranch

Made for: Claude Code.

Or install mainbranch, the plugin that ships this one along with the rest of its 21 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for google-ads-search-launch

README.md
[![agentmods](https://agentmods.dev/badge/skills/noontide-co/mainbranch/google-ads-search-launch/github.svg)](https://agentmods.dev/skills/noontide-co/mainbranch/google-ads-search-launch)
Your own site
<a href="https://agentmods.dev/skills/noontide-co/mainbranch/google-ads-search-launch"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/google-ads-search-launch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for google-ads-search-launch

Your own site · 80×15
<a href="https://agentmods.dev/skills/noontide-co/mainbranch/google-ads-search-launch"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/google-ads-search-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,928 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01928
Opus 5 $0.00022 $0.00964
Sonnet 5 $0.00009 $0.00386
Haiku 4.5 $0.00004 $0.00193

Measured 11d ago against content hash c782f6ab1a6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

google-ads-search-launch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/playbooks/google-ads-search-launch/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Source playbook: playbooks/google-ads-search-launch/playbook.md. This file is the Claude Code playbook shell over that runtime-agnostic source.

This is a reusable draft operating playbook, not a one-off ad checklist. Use it with manual operator judgment when the operator wants to test whether a real offer can turn paid search intent into leads, calls, bookings, deposits, trials, or another concrete business outcome.

It is usable today as a manual recipe and run-record template. It is not a single executable orchestrator, does not automate Google Ads/GTM, and is still collecting evidence from operator runs.

The playbook's job is to turn one offer into one paid-search proof run:

  1. define the bet and success criteria;
  2. prepare or verify the lander and conversion path;
  3. build a tightly scoped Google Ads Search plan;
  4. preserve manual approval gates before spend or provider mutation;
  5. record the run as a push playbook with review evidence and an outcome hook.

It does not publish campaigns, change budgets, upload conversions, publish GTM, or mutate provider accounts. Those steps stay manual or provider-native until a future accepted adapter ships with approval gates and smoke evidence.

Playbook Versus Run

This file is the reusable Noontide recipe: an opinionated paid-search offer-validation sprint. The run belongs in the business repo:

pushes/<push>/playbooks/google-ads-launch-plan.md

Create or update that run file from templates/push-playbook.md. The run file is the approval record, provider-boundary record, launch checklist, review-window record, and outcome hook for a specific offer/push.

This playbook follows the authority model in docs/playbooks.md: official Google Ads docs are the source of truth for platform facts, Main Branch owns the provider boundary and run-record shape, and this file owns the Noontide defaults for testing many offers quickly with tight control. If the operator forks a default, record the fork and reason in the run file.

Read the full file on GitHub · 178 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 178 lines · 43 tokens per session scan A c782f6ab1a6e

Subscribe to this mod's changes

google-ads-search-launch is a skill published in the GitHub repository noontide-co/mainbranch (39 stars, last pushed 27d ago), licensed MIT. It adds 43 tokens to every session and 1,928 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

cn-check

Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.

continuedev/continue · 49 tokens

processing-markdown

Processes Markdown files using mq, a jq-like query language for Markdown. Use when the user mentions Markdown processing, content extraction, document transformation, or mq queries.

harehare/mq · 36 tokens

web-scraping

Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…

harehare/mq · 89 tokens

crit-story

Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.

tomasz-tomczyk/crit · 47 tokens

larksnap-fetch

A bridge for downloading Feishu/Lark documents or ordinary webpages into local files, with options such as Markdown, HTML, or PDF. Feishu, also called Lark, is a workplace collaboration platform.

AmbroseX/larksnap · 111 tokens

suiko

A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.

nwiizo/suiko · 192 tokens