paid-media-ops
Paid Media Operations Skill
Step 0 (always first): Load brand context
Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.
- If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
- If it does not exist: say so, point the user at the template (
templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.
Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.
What This Is
The Paid Media Operations skill brings together 8 specialized agents to manage end-to-end paid advertising for B2B SaaS companies. From strategic budget allocation and campaign setup to daily optimization, creative strategy, and attribution analysis, this team handles Google Ads, LinkedIn Ads, social advertising, programmatic buying, the conversion signal the bidding algorithms learn from, and the media bought directly from publishers — newsletter, podcast and community sponsorships, paid review-site listings, and pay-per-lead content syndication. This skill enables you to achieve predictable cost-per-acquisition, maximize return on ad spend (ROAS), and scale acquisition channels with confidence.