---
title: Advertising Kickoff Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/advertising-kickoff
content_type: text/markdown
description: advertising-kickoff by mbfinotti - This skill runs before paid advertising work and at each recurring review. It routes the task to the right skill.
---

# Advertising Kickoff Skill

Title: Advertising Kickoff Skill for Claude Code

> advertising-kickoff by mbfinotti - This skill runs before paid advertising work and at each recurring review. It routes the task to the right skill.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/advertising-kickoff

This skill runs before paid advertising work and at each recurring review. It routes the task to the right skill in the advertising collection, or says plainly that none fits, and bootstraps or resumes the project's shared context file. A solo founder reaches for it at the start of an ads project to avoid picking the wrong method.

## Key facts

- Installs: 26,673
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill advertising-kickoff`
- Last updated: October 26, 2026

## What Advertising Kickoff does

Routes an advertising task to the right skill in the collection and sets up a shared project context before paid work starts.

Ad work starts without context and uses the wrong method.

Routed tasks and a shared project context.

Best for: Founders starting or resuming a paid advertising project.

Not for: Non-advertising projects.

- Routes tasks to the right advertising skill
- Bootstraps or resumes the shared context file
- Runs at project start and each recurring review

## SKILL.md

## Advertising Kickoff

You are the entry point and router for the 31-skill advertising-skills collection. Route the current paid-advertising task to exactly one sibling skill - or say plainly that none fits - and make the next session start warm instead of cold. Routing is the reason this skill exists; everything else here serves it.

Run this skill at every project start, even when the collection's skills are already used daily in another context - a new project is a new context, and daily familiarity with siblings does not replace the kickoff pass. On later sessions of the same project, re-run it to resummarize and re-route, never to re-interview. Everything in this skill works identically for B2B and B2C accounts; only the routing outcomes differ, and the sibling scopes say so where they do.

### 1. Detect before asking

Every fact derivable from the environment is a question the user never has to answer. Run detection first; the interview cap only survives if it does.

1. Decide cold vs warm start from one signal only: does `advertising-context.md` exist in the project? Present → warm. Absent → cold. Never ask the user which mode it is.
2. If you can read the repository's git history, read the recent log to infer stage and pace: commit frequency, what changed last, whether work stalled.
3. Inventory existing files - README, agent-instruction files, briefs, past campaign docs, media plans - so nothing already written gets re-asked.
4. If your harness exposes connectors or integrations, detect which are available - an ad-account export, an analytics source, a CRM, a creative asset store - and let their presence shape routing and routines. Describe the capability; never assume a specific product.
5. If the collection ships readable version metadata, note what changed since the last session. If it doesn't - the common case - degrade silently. Never block, warn, or ask about versions.

### 2. Interview - capped, tappable

On a cold start:

- Ask at most 5-7 questions.
- Ask one question per message.
- Offer multiple-choice options whenever possible.
- Spend questions only where detection came up empty - skip any question the file inventory or git log already answered.

1. "What are we selling, and to whom?" - (a) B2B sales-led, (b) B2B self-serve, (c) B2C, (d) both/mixed. B2B and B2C answers steer different siblings later, so this comes first.
2. "What is the goal of this session - and is it the same as the project's goal?" Ask on both cold and warm starts; a project goal never substitutes for today's goal.
3. "Which channels are you buying today, and what's the monthly spend band?" - (a) not spending yet, (b) under $5k, (c) $5k-50k, (d) over $50k; list the channels free-form.
4. "What conversion event counts as success, and where does the source of truth live?" - platform pixel, analytics tool, CRM, or order system.
5. "Any hard constraints, and is there a date the result has to land by?" - (a) committed budgets or an agency contract, (b) a fixed date - seasonal peak, launch, board review: give the date, (c) regulated vertical / compliance review, (d) no creative production capacity, (e) none.
6. "Do you want a one-off win out of this session, or a compounding asset - and what is your effort ceiling?" - (a) one-off, hours only, (b) one-off, a week of work is fine, (c) compounding, a few hours every week from here, (d) compounding, and I can commit headcount or executive sign-off.
7. "What is already decided, and what is still open?" - one line each; decided items are off the table for re-litigation.

Questions 5 and 6 exist to order the output, not to describe the project: the landing date, the one-off-versus-compounding answer and the effort ceiling are what re-rank the short-list and the routines (see § 4 and § 7). Ask them here, never beside a ranking - by then the user has already committed to a path. Record all three in the artifact so the warm start re-ranks without re-asking.

On a warm start, ask only the session-goal question. Everything else comes from the artifact.

### 3. Route the task

Match the stated session goal against the declared scope of each skill below. Route to exactly one skill for the immediate task. Never force a match: when nothing fits, say so and name the gap instead of stretching the nearest skill.

This table is deliberately unranked, and must stay that way. Scope is a match test, not a ratio: ordering the rows would invent a preference between skills that never compete for the same task. Ranking belongs one step later, in the short-list (§ 4).

| Skill                                                    | Route here when the task is…                                                                                                                           |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `mbfinotti/advertising-skills@ad-account-diagnostic`     | Find the root cause of an underperforming ad account across tracking, structure, targeting, creative, bidding, offer; "why are my ads underperforming" |
| `mbfinotti/advertising-skills@ad-copy-variants`          | Turn one value proposition into distinct static/text copy variants labelled by angle and awareness stage; search headline sets                         |
| `mbfinotti/advertising-skills@ad-format-fit`             | Flag poor-fit or misused ad formats for a stated objective on a chosen platform, pre-launch format QA; format vs creative problem post-launch          |
| `mbfinotti/advertising-skills@ad-swipe-file`             | Collect competitors' currently-running ads into a categorized library and rank creative test hypotheses                                                |
| `mbfinotti/advertising-skills@advertising-career`        | Candidate side: skill-gap roadmap, interview prep, NDA-safe portfolio, agency vs in-house, pay conversations                                           |
| `mbfinotti/advertising-skills@advertising-hiring`        | Hirer side: rung decision, scorecard, interview loop, work sample, 30-60-90 with staged spend authority                                                |
| `mbfinotti/advertising-skills@advertising-radar`         | What to read/follow to stay current: a time-budgeted watch list of paid-advertising sources                                                            |
| `mbfinotti/advertising-skills@ad-attribution-gap`        | Quantify and explain discrepancies between platform reporting, analytics, and the source of truth; "the numbers don't match"                           |
| `mbfinotti/advertising-skills@ad-audience-targeting`     | Turn an ICP and buying signals into a layered targeting plan sized against platform floors, with exclusion rules                                       |
| `mbfinotti/advertising-skills@ad-bidding-strategy`       | Choose the bid policy per platform and goal, set and move the target, evaluation window, rollback trigger; "target CPA or target ROAS"                 |
| `mbfinotti/advertising-skills@ad-budget-pacing`          | Track daily/weekly spend against an already-set budget and flag under/over-pacing; "am I on pace"                                                      |
| `mbfinotti/advertising-skills@ad-buyer-group-mapper`     | Map the buying committee for an offer and give each role a messaging angle plus an ad-targeting proxy                                                  |
| `mbfinotti/advertising-skills@cac-roas-benchmark`        | Compute CAC/ROAS from real data and judge spend health against break-even, own history, external benchmarks; "is my CAC too high"                      |
| `mbfinotti/advertising-skills@ad-campaign-consolidation` | Plan which campaigns/ad sets to merge without resetting learning; "too many ad sets", "stuck in learning"                                              |
| `mbfinotti/advertising-skills@conversational-ad-copy`    | Ad copy for a single response slot inside an AI-assistant reply or answer-engine result                                                                |
| `mbfinotti/advertising-skills@ad-conversion-tracking`    | Pre-launch GO/NO-GO check that conversion events are configured, firing once, deduplicated; "is my tracking working"                                   |
| `mbfinotti/advertising-skills@ad-creative-brief`         | Turn a campaign goal plus an audience insight into a brief a designer, editor, or creator executes                                                     |
| `mbfinotti/advertising-skills@ad-creative-fatigue`       | Verdict on whether a running creative is genuinely worn out or a confounder explains the decline; "should I kill this ad"                              |
| `mbfinotti/advertising-skills@ad-creative-test-plan`     | Design a pre-launch creative test: hypothesis, cells, budgets, sample, pre-registered kill/scale rules                                                 |
| `mbfinotti/advertising-skills@ad-hook-analyzer`          | Score and force-rank the openings of candidate video ads before launch; "which hook should I test"                                                     |
| `mbfinotti/advertising-skills@paid-landing-page-audit`   | Audit a landing page receiving paid traffic and return a prioritised fix list; "clicks but no conversions"                                             |
| `mbfinotti/advertising-skills@lookalike-audience-seeds`  | Select and size the seed customer list behind a lookalike/value-based audience; match rate, platform floor                                             |
| `mbfinotti/advertising-skills@paid-media-scaling`        | Decide when a proven campaign has earned a budget increase, the step size, the ramp, rollback triggers                                                 |
| `mbfinotti/advertising-skills@ad-negative-keywords`      | Build and maintain negative keyword lists from search term reports; exclusion levels, review cadence                                                   |
| `mbfinotti/advertising-skills@ad-platform-selection`     | Choose which paid channel families fit the business's economics, audience, funnel stage, and budget at setup                                           |
| `mbfinotti/advertising-skills@ad-spend-guardrails`       | Write the org's spend policy: max allowable CAC, min ROAS floor, kill switches, ownership, override rights                                             |
| `mbfinotti/advertising-skills@retargeting-funnel`        | Design a staged retargeting sequence: recency windows, depth tiers, message ladder, exclusions, frequency caps                                         |
| `mbfinotti/advertising-skills@ad-spend-allocation`       | Split a fixed total budget across campaigns, platforms, funnel stages, and audiences by expected marginal return                                       |
| `mbfinotti/advertising-skills@thought-leadership-ads`    | Plan a campaign promoting an executive's existing organic posts as paid person-fronted ads                                                             |
| `mbfinotti/advertising-skills@ugc-ad-scripts`            | Write UGC-style short-form video ad scripts a creator can film, with hook variants and delivery notes                                                  |
| `mbfinotti/advertising-skills@advertising-kickoff`       | This skill: project start, periodic check-in, "which skill do I need", re-routing                                                                      |

Three clusters collide hard on keywords and demand disambiguation before routing:

- the hirer-vs-candidate mirror pair
- the six-skill budget cluster
- the six-skill creative cluster

Disambiguate strictly from each skill's declared scope, never from a guess about what a skill "probably" covers: a wrong disambiguation misroutes worse than none. Read `references/skill-routing.md` for the per-skill route/do-not-route signals, all boundary-pair disambiguations, the ordered chains, and the named coverage gaps, before routing any task that could plausibly match two skills.

Name the gap explicitly when the task needs something no skill covers. Collection v1 has no skill for:

- positive keyword research
- in-platform execution of any kind
- creative production itself
- incrementality testing or media mix modeling
- cross-channel budgeting beyond paid ads
- post-signup activation
- ad policy appeals and suspension recovery
- product feed management

Say "the collection has no skill for this" - never promise a skill exists or invent one.

### 4. Output shape

Deliver the routing result in this shape, every time:

1. **State summary** (warm start only) - exactly 5 lines from the artifact: business model and channels, spend band, conversion source of truth, in-flight work, active constraint.
2. **Route** - the one skill for the immediate task (or "no skill fits", plus the named gap).
3. **Short-list** - 5 to 8 skills relevant to this project right now, ordered by value returned per unit of effort, highest ratio first. Give each entry one line naming both sides: the bottleneck it attacks, and what the session costs. Never order by cheapness and never by the routing table's row order - see "Ordering the short-list" below.
4. **Chain** - when the task genuinely decomposes into an ordered sequence (e.g. `mbfinotti/advertising-skills@ad-platform-selection` → `mbfinotti/advertising-skills@ad-format-fit` → `mbfinotti/advertising-skills@ad-conversion-tracking` → `mbfinotti/advertising-skills@ad-creative-test-plan`), list it in execution order with one line per link on what it hands to the next. Chain order is dependency order, not efficiency order - a later link cannot run before its earlier one, so ranking a chain adds nothing. Omit the chain when there isn't one - never fabricate a sequence.
5. **Not now** - skills that will matter later, each with its explicit unblocking condition (e.g. "`mbfinotti/advertising-skills@paid-media-scaling` - after `mbfinotti/advertising-skills@cac-roas-benchmark` returns a healthy verdict").
6. **Gap** - anything today's task needs that no skill covers, stated as a gap.

#### Ordering the short-list

The user's question at that moment is never "which of these exists" but "which one do I run first, and is it worth the session". Only a ratio answers that. Default class order, highest value/effort ratio first:

1. **Measurement integrity** - `mbfinotti/advertising-skills@ad-conversion-tracking`, `mbfinotti/advertising-skills@ad-attribution-gap`. Buys back the readability of every number in the account, so every later session is measured through it. Costs hours to a day, mostly one engineer's, and it is done.
2. **Diagnosis** - `mbfinotti/advertising-skills@ad-account-diagnostic`, `mbfinotti/advertising-skills@cac-roas-benchmark`. Buys a named failing layer instead of a guess. Costs one session on data already in hand and implements nothing, which is what stops a week going into the wrong layer.
3. **Policy and structure** - `mbfinotti/advertising-skills@ad-spend-guardrails`, `mbfinotti/advertising-skills@ad-platform-selection`, `mbfinotti/advertising-skills@ad-spend-allocation`, `mbfinotti/advertising-skills@ad-campaign-consolidation`. Buys a ceiling on how wrong a month can go, and volume for starved units. Costs a session plus stakeholder sign-off; cheap to write, expensive to un-merge in the account.

Excerpt. The rest of the file is on the canonical page and in the source repository.

## Advertising Kickoff FAQ

### Is Advertising Kickoff safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

## Machine access

- [Sitemap](https://skillselion.com/sitemap.xml)
- [llms.txt](https://skillselion.com/llms.txt)
- [llms-full.txt](https://skillselion.com/llms-full.txt)
- [Developer resources](https://skillselion.com/developers)
- [OpenAPI spec](https://skillselion.com/openapi.json)
- [MCP handshake](https://skillselion.com/.well-known/mcp)
- [API catalog](https://skillselion.com/.well-known/api-catalog)
- [AI catalog](https://skillselion.com/.well-known/ai-catalog.json)
- [Pricing](https://skillselion.com/pricing.md)
- [Auth](https://skillselion.com/auth.md)
- [AGENTS.md](https://skillselion.com/AGENTS.md)
- [Contact](https://skillselion.com/contact)
- [Home](https://skillselion.com/)
