ads-pimp

Active router for ALL paid advertising requests — Meta Ads, Pinterest Ads, Conversions API, CAPI, audience management. Organic social goes to social-pimp.

Model	Source
sonnet	pack: ads

Full Reference

If the request involves paid advertising in ANY way — Meta Ads, Pinterest Ads, Conversions API, CAPI, server-side events, audience management, ad creative, ad campaigns, Meta Marketing API, Pinterest API, auth token verification — you MUST route through this skill FIRST.

Organic Facebook Page posts, organic Instagram publishing, and Google Business Profile management are NOT this skill. Those go to social-pimp.

This is not optional. This is not negotiable. You cannot skip this.

Ads Pimp

The orchestration layer for all paid advertising expertise. Not documentation — an active router. Every paid ads request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 📢 ads-pimp ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of what request/routing] ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No exceptions. Box frame first, then route.

Quick Context

The ads pack covers paid social campaign management across Meta and Pinterest — campaign creation, audience targeting, server-side Conversions API integration, and auth verification.

Not in scope: Organic Facebook Page posts → meta-pages. Organic Instagram publishing → instagram-api. Google Business Profile → google-business-profile-api. All three route via social-pimp.

Routing Table

Classify the request. Invoke the matching skill. No response before invocation.

Request Pattern	Skill
Meta Ads campaigns, ad sets, ad creative, Meta Marketing API	`meta-ads`
Meta custom audiences, lookalike audiences, audience management	`meta-audiences`
Meta Conversions API, CAPI, server-side events, event dedup	`meta-conversions`
Meta Graph API reference, API version, rate limits, auth flows	`meta-api-reference`
Pinterest Ads, Pinterest campaigns, promoted pins	`pinterest-ads`
Pinterest API reference, OAuth, token refresh, rate limits	`pinterest-api-reference`
Verify Meta auth tokens, debug Meta API permissions	`verify-meta-auth`
”How do I set up ads?” / “Which ads platform should I use?”	Decision matrix → route

Decision Matrix

When the user hasn’t specified a platform or sub-topic:

Signal	Route To
Meta / Facebook / Instagram campaigns, creatives, ad sets	`meta-ads`
Custom audiences, lookalikes, audience targeting, retargeting	`meta-audiences`
Server-side events, CAPI, pixel deduplication, conversion tracking	`meta-conversions`
Graph API endpoints, rate limits, versioning, API reference (Meta)	`meta-api-reference`
Pinterest campaigns, promoted pins, shopping ads	`pinterest-ads`
Pinterest API docs, token refresh, OAuth reference	`pinterest-api-reference`
Token expired, auth error, access token validation	`verify-meta-auth`

Shortcut rules:

Meta campaign creation → meta-ads, no discussion
Custom audience or lookalike → meta-audiences, no discussion
Server-side conversion event → meta-conversions, no discussion
Pinterest ad campaign → pinterest-ads, no discussion
Auth/token problem → verify-meta-auth, no discussion
API endpoint lookup → platform-specific reference skill, no discussion

State Detection

Before routing, check project context:

package.json → detect facebook-nodejs-business-sdk already installed
.env / .env.example → detect META_ACCESS_TOKEN, PINTEREST_ACCESS_TOKEN present

State	Action
`facebook-nodejs-business-sdk` in deps	Route Meta requests to `meta-ads` directly
`META_ACCESS_TOKEN` in env	Meta platform confirmed — skip platform selection
`PINTEREST_ACCESS_TOKEN` in env	Pinterest platform confirmed — skip platform selection
Nothing detected	Apply decision matrix

Chaining Patterns

User Says	Chain
”Set up Meta Ads tracking”	`meta-conversions` → `meta-ads`
”My Meta token isn’t working”	`verify-meta-auth` → `meta-api-reference`
”Set up Pinterest campaigns”	`pinterest-ads` → `pinterest-api-reference`
”Create lookalike audiences”	`meta-audiences`
”Implement server-side events”	`meta-conversions`
”Set up full Meta ads stack”	`verify-meta-auth` → `meta-ads` → `meta-conversions`
”Duplicate a campaign to Pinterest”	`meta-ads` then `pinterest-ads`

Hard Rules

Never respond about ads/social before invoking the target skill
No summarizing, planning to invoke, or explaining what you’re about to do
If unclear, ask ONE clarifying question, then route
The skill’s content has the verified facts — always defer to it
Meta token issues always go through verify-meta-auth before any campaign work
“How do I run ads?” is decision matrix territory — NEVER jump to implementation