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.
- Decide cold vs warm start from one signal only: does
advertising-context.mdexist in the project? Present → warm. Absent → cold. Never ask the user which mode it is. - 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.
- Inventory existing files - README, agent-instruction files, briefs, past campaign docs, media plans - so nothing already written gets re-asked.
- 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.
- 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: