advertising-kickofflisted

Before starting any paid advertising work, before each recurring advertising review, and whenever routing is unclear, route the task to the right skill of the advertising-skills collection - or say plainly that none fits - and bootstrap or resume the project's shared context artifact. Use at every advertising project start, on later sessions of the same project to re-route without re-interviewing, and whenever the user mentions a new ad campaign or paid media project, asks which advertising skill they need, or wants a periodic advertising check-in - even if they name no skill at all. Prefer this whenever several skills could apply, since the collection has three colliding clusters - the hirer-vs-candidate pair, the budget cluster, the creative cluster - and it returns a short-list plus an ordered skill chain rather than a single guess. Do NOT use when the task already maps cleanly to one skill, such as a pure account audit - that is mbfinotti/advertising-skills@ad-account-diagnostic.
mbfinotti/advertising-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill mbfinotti/advertising-skills

# 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 i