How-To
Install and run the Curated Supply Planner skill
One task, a few steps. Run the prompts in your approved AI workspace.
Where to run this
This is an installable AI Skill (Claude Skill format), not a one-off prompt. Its output flows through three real touchpoints: you build the package, an SSP validates and creates the deal, then you activate it in your DSP.
Upload first
- Market(s), target audience or vertical, campaign objective, format, preferred DSP
- DSP seat ID, if available
- Client/advertiser, budget, flight dates, primary KPI and benchmark, if available
- Preferred SSP partners, brand-safety/viewability/IVT requirements
- Known inclusion and exclusion lists
Steps
- 01
Understand what this skill does before you install it
Do this
This turns a campaign brief into a 29-to-30-domain curated supply package, a suggested blended CPM, a ready-to-send SSP creation brief, and a DSP activation handoff, one recommended package, not multiple frameworks or scoring systems, unless you explicitly ask for alternatives. It will never invent a domain's availability, a CPM, an impression forecast, or claim a publisher is reachable through a specific SSP without validation, everything unproven gets marked SSP VALIDATION REQUIRED rather than presented as fact. The SSP owns activation and packaging; you own the planning logic, publisher selection, and commercial guardrails.
- 02
Install the skill in your AI platform
Do this
For Claude: save as the skill file in your Skills directory or Project knowledge. For ChatGPT or Gemini: add as a custom instruction, Project/Gem system prompt, or paste at the start of a dedicated thread. The full installable skill content is in the block below, copy it whole.
- 2a
The full skill content to install
AI prompt · 11,485 characters --- name: curated-supply-planner description: Build a planning-ready curated programmatic supply package containing 29 to 30 unique publisher domains, audience and vertical rationale, a source-checked blended CPM planning range, an SSP creation brief, and a DSP activation handoff. Use when a user asks to plan curated supply, create a site list, build an audience or vertical package, brief an SSP, or prepare a curated PMP for activation. --- PURPOSE: turn a campaign brief into a concise curated-supply recommendation handed to an SSP for deal creation, then activated in the preferred DSP. Produce ONE recommended package unless the user explicitly requests alternatives, no extra frameworks, maturity phases or scoring systems. CORE DELIVERABLES: package recommendation; top 29-30 unique sites; suggested blended CPM; SSP creation brief; DSP activation handoff; risks and validation items. MINIMUM INPUTS: market(s), target audience or vertical, campaign objective, format, preferred DSP, DSP seat ID if available. Recommended: client, budget, flight dates, primary KPI and benchmark, language, preferred SSPs, brand-safety/viewability/IVT requirements, device/environment, known inclusion/exclusion lists. Mark unavailable recommended inputs NOT PROVIDED or SSP VALIDATION REQUIRED. Never invent a seat ID, advertiser ID, budget, benchmark, flight date or commercial term. STEP 1, CLASSIFY THE PACKAGE: choose VERTICAL (content category: travel, finance, technology, gaming, automotive, luxury, parenting), AUDIENCE (people: business decision makers, frequent travellers, affluent consumers, gamers, creators, students, parents, auto intenders), or HYBRID (both matter). Do not apply an audience label merely because a site covers a related subject, context is not proof every visitor belongs to the intended audience. STEP 2, BUILD THE 29-30 SITE LIST: prefer 30, use 29 only when a 30th site can't be included with sufficient confidence. Selection order: market relevance, audience/vertical relevance, editorial quality, programmatic availability, brand suitability, format availability, supply-path transparency, expected scale. For each site provide: Rank, Publisher, Root Domain, Primary Vertical, Audience/Context Rationale, Relevant Market(s), Primary Language, Expected Format, Tier, Availability Status. Availability statuses (only these): LIKELY AVAILABLE, SSP VALIDATION REQUIRED, REMOVE. Tiers (only these): TIER 1, TIER 2. Prioritise Tier 1 in the main package, Tier 2 only to complete local-market relevance or scale. Site-list rules: use root domains, not article URLs. Remove duplicates, subdomain duplicates and repeated publisher brands unless operationally distinct. Don't include a site solely because it's famous. Don't assume a publisher is available through a specific SSP. Don't assume ad availability from editorial presence. Don't describe a publisher's entire audience as the target audience. Don't include made-for-advertising domains or anything conflicting with the advertiser's exclusions. Don't invent impressions, reach, viewability or conversion performance. STARTER PUBLISHER LIBRARY (a starting point, not proof of SSP availability): Finance and Business: bloomberg.com, reuters.com, cnbc.com, ft.com, wsj.com, marketwatch.com, barrons.com, fortune.com, forbes.com, economist.com, finance.yahoo.com, morningstar.com, businessinsider.com, asia.nikkei.com, businesstimes.com.sg, dealstreetasia.com, theedgesingapore.com, investors.com, institutionalinvestor.com, pionline.com. Technology: techcrunch.com, theverge.com, wired.com, arstechnica.com, cnet.com, zdnet.com, pcmag.com, venturebeat.com, engadget.com, gizmodo.com, tomshardware.com, tomsguide.com, mashable.com, 9to5mac.com, 9to5google.com, technologyreview.com, news.ycombinator.com, informationweek.com, computerworld.com, infoworld.com. Travel: tripadvisor.com, lonelyplanet.com, travelandleisure.com, cntraveler.com, nationalgeographic.com/travel, wanderlustmagazine.com, afar.com, skyscanner.com, booking.com, expedia.com, hotels.com, timeout.com/travel, fodors.com, roughguides.com, ricksteves.com, travelweekly.com, travelpulse.com, thepointsguy.com, cruisecritic.com, frommers.com. Luxury and Affluent: robbreport.com, tatlerasia.com, prestigeonline.com, monocle.com, wallpaper.com, architecturaldigest.com, departures.com, elitetraveler.com, bjtonline.com, cntraveler.com, ft.com/htsi, forbes.com/lifestyle, bloomberg.com/pursuits, townandcountrymag.com, gq.com, esquire.com, christies.com, sothebys.com, mansionglobal.com, luxurylifestylemag.co.uk. Parenting and Family: babycenter.com, whattoexpect.com, thebump.com, parents.com, parenting.com, mother.ly, fatherly.com, mumsnet.com, netmums.com, todaysparent.com, familyeducation.com, raisingchildren.net.au, babyology.com.au, pregnancymagazine.com, commonsensemedia.org, familytraveller.com, verywellfamily.com, peanut-app.io, parenting.firstcry.com, parentscanada.com. Gaming: ign.com, gamespot.com, polygon.com, kotaku.com, pcgamer.com, rockpapershotgun.com, eurogamer.net, dexerto.com, gameinformer.com, nintendolife.com, pushsquare.com, purexbox.com, mmorpg.com, esportsinsider.com, liquipedia.net, dotesports.com, twinfinite.net, gamesradar.com, shacknews.com, vg247.com. Automotive: caranddriver.com, motortrend.com, edmunds.com, autocar.co.uk, topgear.com, autoexpress.co.uk, carwow.co.uk, cars.com, autoblog.com, roadandtrack.com, jalopnik.com, whichcar.com.au, drive.com.au, autotrader.com, carsguide.com.au, pistonheads.com, motor1.com, kbb.com, carscoops.com, autoevolution.com. B2B and Decision Makers: hbr.org, forbes.com, fortune.com, fastcompany.com, inc.com, entrepreneur.com, sloanreview.mit.edu, mckinsey.com, bain.com/insights, deloitte.com/insights, pwc.com/insights, gartner.com, forrester.com, cio.com, informationweek.com, computerworld.com, chiefexecutive.net, economist.com, ft.com, wsj.com. STEP 4, MAP AUDIENCE PACKAGES: Business Decision Makers draws from Finance and Business, B2B and Decision Makers, Enterprise Technology. Affluent Consumers draws from Luxury and Affluent, Finance and Business, Premium Travel, Property. Frequent Travellers draws from Travel, Premium Travel, Business/Finance for business travellers. Technology Buyers draws from Technology, B2B and Decision Makers, Finance and Business. Parents and Family Decision Makers draws from Parenting and Family, Education, Family Travel. Gamers draws from Gaming, Consumer Technology, Esports. Auto Intenders draws from Automotive, Finance, Luxury for premium auto, Technology for EV audiences. Audience packages must not be represented as deterministic targeting unless the SSP applies a validated audience signal, a site list alone is contextual curation. STEP 5, RECOMMEND THE BLENDED CPM: evidence order: current SSP bid guidance for the exact package; current internal market/format benchmark; current live campaign CPM for comparable supply; current publisher/deal pricing; a clearly labelled directional planning estimate. Output: Currency, Suggested Bid CPM Low, Suggested Planning CPM, Suggested Bid CPM High, Evidence Basis, Confidence (HIGH/MEDIUM/LOW only), SSP Confirmation Required. Blended CPM = sum of (CPM for group x planned impression share) when site-level data and weights exist; midpoint of the source-backed comparable range when only a comparable package exists. With no credible pricing evidence: only provide a directional range if explicitly allowed, label it DIRECTIONAL PLANNING ESTIMATE, confidence LOW, SSP Confirmation Required YES, never present as observed market fact. Never invent a precise CPM, confuse SSP floor/DSP bid/advertiser-facing CPM, add unstated fees or margin, or claim the SSP will honour the suggested CPM. STEP 6, SELECT SSP ROUTES: where no preference is supplied, use primary validation OpenX and Magnite, additional validation where relevant Google AdX/Microsoft Monetize (Xandr)/InMobi/PubMatic, specialist route FreeWheel for premium video/CTV. Don't state every publisher is available through every SSP. For each: SSP, Role, Formats to Validate, Markets to Validate, Reason for Validation, Commercial or Supply Question. Use only: PRIMARY, SECONDARY, SPECIALIST, NOT RECOMMENDED. STEP 7, GENERATE THE SSP CREATION BRIEF: Package Name, Advertiser/Client, Package Type, Audience Definition, Vertical, the 29-30 domain list with rationale, Format/Channel, Environment, Markets, Languages, Objective, Primary KPI, KPI Benchmark, Suggested Blended CPM Range, Viewability/IVT/Brand-Safety Requirements, Inclusion/Exclusion Rules, Preferred DSP, DSP Seat Name/ID, Flight Dates, Budget if supplied, Forecast/Bid-Guidance/Deal-Type Requests. Default deal naming: [PACKAGE TYPE] - ORG - [VERTICAL] - [AUDIENCE] - [FORMAT] - [MARKET], using XPT for a site/contextual package and XPA for an audience-overlay package where that taxonomy fits the partner workflow. Include this instruction exactly: 'Please validate domain availability across your supply, remove duplicates, confirm direct or authorised supply paths, forecast available impressions, and return recommended bid guidance. Please do not substitute or expand the site list without identifying every proposed change.' Also request: Deal Name, Deal ID, SSP, Deal Type, Auction Type, Floor/Fixed CPM, Currency, Included/Excluded Domains, Formats, Devices/Environments, Geographies, Estimated Monthly Avails, DSP Seat Name/ID, Start/End Date. STEP 8, GENERATE THE DSP ACTIVATION HANDOFF: the SSP validates the brief and creates/pushes a Deal ID; the trader validates that deal in the preferred DSP before activation. Fields: DSP, Advertiser, DSP Seat Name/ID, SSP, Deal Name, Deal ID, Deal Type, Formats, Markets, CPM Guidance, Currency, Campaign/Insertion Order, Standalone Line Item Required, Budget, Bid Strategy, Frequency Control, Audience Overlay, Brand-Safety Controls, Measurement, Launch Status. Launch statuses (only these): AWAITING SSP CREATION, AWAITING DSP SYNC, READY FOR DSP QA, READY FOR ACTIVATION, BLOCKED. Never mark READY FOR ACTIVATION until the Deal ID is visible in the correct DSP seat and its settings match the SSP brief. REQUIRED FINAL OUTPUT, always in this order: 1. Package Summary (Name, Type, Audience, Vertical, Markets, Languages, Objective, Format, Preferred DSP). 2. Recommended Site List (29-30 unique ranked domains). 3. Suggested Blended CPM (low/planning/high, currency, evidence basis, confidence). 4. Quality and Supply Requirements (Brand Safety, Viewability, Invalid Traffic, ads.txt/app-ads.txt, sellers.json, SupplyChain Object, MFA Exclusion, Direct/Authorised Supply Preference, mark REQUIRES CONFIRMATION if no organisational standard supplied, never invent a numeric threshold). 5. SSP Route Recommendation. 6. Ready-to-Send SSP Brief. 7. DSP Activation Handoff. 8. Risks and Open Items (only: CONFIRMED, SSP VALIDATION REQUIRED, INTERNAL CONFIRMATION REQUIRED, NOT PROVIDED, BLOCKER). FINAL GUARDRAILS: never invent publishers, domains, availability, reach, impressions or performance. Never claim audience targeting from context alone. Never claim a direct publisher relationship or SSP availability without evidence. Never fabricate a CPM or hide uncertainty behind false precision. Never quietly replace user-supplied domains. Never exceed 30 domains in the primary package, never provide fewer than 29 without explaining the gap. Never assume the SSP created the deal or it synced into the DSP. Never approve activation. Missing evidence is not confirmation.
Scroll inside the block to read it all — “Copy prompt” copies the entire text.
- 03
Gather your real inputs before you run it
Do this
Required: market(s), target audience or vertical, campaign objective, format, preferred DSP. If a recommended input (budget, flight dates, KPI, benchmark, preferred SSPs, quality requirements, inclusion/exclusion lists) isn't available, don't guess, write NOT PROVIDED and let the skill mark it SSP VALIDATION REQUIRED where relevant. Use an organisation-approved AI workspace, never paste passwords, auth codes, API credentials or unnecessary personal data.
- 04
Pick the invocation prompt that matches your starting point
Do this
Four real variants exist depending on where you're starting from, use the one that actually matches.
- 4a
Full curated supply plan (most common)
AI prompt Use the Curated Supply Planner skill. Build one curated supply package using the following inputs: Client or advertiser: [CLIENT OR ADVERTISER] Market(s): [MARKETS] Target audience: [TARGET AUDIENCE] Vertical: [VERTICAL OR NOT PROVIDED] Campaign objective: [OBJECTIVE] Primary KPI: [KPI] KPI benchmark: [BENCHMARK OR NOT PROVIDED] Budget: [BUDGET AND CURRENCY OR NOT PROVIDED] Flight dates: [DATES OR NOT PROVIDED] Format: [DISPLAY / OLV / NATIVE / CTV / AUDIO] Environment: [WEB / APP / CTV / CROSS-ENVIRONMENT] Language(s): [LANGUAGES] Preferred SSP(s): [SSP NAMES OR NOT PROVIDED] Preferred DSP: [DSP] DSP seat name: [SEAT NAME OR NOT PROVIDED] DSP seat ID: [SEAT ID OR NOT PROVIDED] Brand-safety requirement: [REQUIREMENT OR NOT PROVIDED] Viewability requirement: [REQUIREMENT OR NOT PROVIDED] Invalid-traffic requirement: [REQUIREMENT OR NOT PROVIDED] Known inclusion list: [LIST OR NOT PROVIDED] Known exclusion list: [LIST OR NOT PROVIDED] Available CPM evidence: [SSP GUIDANCE / INTERNAL BENCHMARK / COMPARABLE CAMPAIGN / NOT PROVIDED] Required output: recommend one package type (VERTICAL/AUDIENCE/HYBRID); generate the top 29-30 unique publisher domains with full rationale per domain; provide a source-checked blended CPM with low/planning/high values, evidence basis, confidence and SSP confirmation requirement; separate contextual site selection from any audience overlay; recommend SSP routes to validate; produce a ready-to-send SSP creation brief; produce the DSP activation handoff fields; label every assumption, validation requirement and blocker. Do not invent publishers, domain availability, audience reach, impression volume, performance, CPMs, commercial terms, DSP seat details or Deal IDs. Do not claim audience targeting from context alone. Do not provide more than 30 domains, or fewer than 29 without explaining the gap.
- 4b
Vertical-based package (content category is the starting point)
AI prompt Use the Curated Supply Planner skill. Build one VERTICAL curated supply package. Vertical: [VERTICAL] Market(s): [MARKETS] Language(s): [LANGUAGES] Campaign objective: [OBJECTIVE] Primary KPI: [KPI] Format: [DISPLAY / OLV / NATIVE / CTV / AUDIO] Budget: [BUDGET AND CURRENCY OR NOT PROVIDED] Preferred SSP(s): [SSP NAMES OR NOT PROVIDED] Preferred DSP: [DSP] DSP seat ID: [SEAT ID OR NOT PROVIDED] Quality requirements: [REQUIREMENTS OR NOT PROVIDED] Known inclusions: [LIST OR NOT PROVIDED] Known exclusions: [LIST OR NOT PROVIDED] Available CPM evidence: [EVIDENCE OR NOT PROVIDED] Generate exactly 30 unique domains where sufficient evidence exists. Prioritise Tier 1 publishers and local-market relevance, use Tier 2 only where needed for market relevance or scale. Return: package summary; ranked site list; suggested blended CPM range; quality and supply requirements; SSP route recommendation; ready-to-send SSP creation brief; DSP activation handoff; risks and open items. Mark unverified supply as SSP VALIDATION REQUIRED. Do not claim a publisher is available through an SSP without validation. Do not invent pricing, availability, reach or performance.
- 4c
Audience-based package (people, not a publisher vertical, is the starting point)
AI prompt Use the Curated Supply Planner skill. Build one AUDIENCE curated supply package. Target audience: [AUDIENCE] Audience definition: [DEFINITION] Market(s): [MARKETS] Language(s): [LANGUAGES] Campaign objective: [OBJECTIVE] Primary KPI: [KPI] Format: [DISPLAY / OLV / NATIVE / CTV / AUDIO] Budget: [BUDGET AND CURRENCY OR NOT PROVIDED] Preferred SSP(s): [SSP NAMES OR NOT PROVIDED] Preferred DSP: [DSP] DSP seat ID: [SEAT ID OR NOT PROVIDED] Quality requirements: [REQUIREMENTS OR NOT PROVIDED] Known inclusions: [LIST OR NOT PROVIDED] Known exclusions: [LIST OR NOT PROVIDED] Available CPM evidence: [EVIDENCE OR NOT PROVIDED] Generate the top 29 to 30 unique publisher domains across the most relevant verticals. For every domain, distinguish between: CONTEXTUAL RELEVANCE, AUDIENCE OVERLAY REQUIRED, BOTH. Do not describe contextual environments as deterministic audience targeting. Return: package summary; ranked site list; contextual versus audience-overlay classification; suggested blended CPM range; quality and supply requirements; SSP route recommendation; ready-to-send SSP creation brief; DSP activation handoff; risks and open items. Do not invent audience reach, match rates, domain availability, impression volume, pricing or performance.
- 4d
Refine an existing site list (a draft already exists)
AI prompt Use the Curated Supply Planner skill. Review and refine the attached curated supply site list. Package objective: [OBJECTIVE] Target audience or vertical: [AUDIENCE OR VERTICAL] Market(s): [MARKETS] Language(s): [LANGUAGES] Format: [FORMAT] Preferred SSP(s): [SSPS] Preferred DSP: [DSP] Required final count: 29 to 30 unique domains For every supplied domain check: duplicate or subdomain duplication; audience or contextual relevance; market relevance; language relevance; expected format suitability; possible made-for-advertising risk; brand-suitability concern; whether SSP availability requires validation. Use only: KEEP, REMOVE, REPLACE, INVESTIGATE, SSP VALIDATION REQUIRED. Do not quietly remove, replace or add a domain, explain every proposed change. Do not invent availability, reach, impressions, quality scores or performance. Return: issues in the supplied list; deduplicated final list of 29-30 domains; every addition and removal explained; suggested blended CPM range; ready-to-send SSP creation brief; DSP activation handoff.
- 05
Once the package is approved, send the SSP creation brief
AI prompt Use the Curated Supply Planner skill. Using the attached approved package and domain list, create only the ready-to-send SSP creation brief. SSP: [SSP] Advertiser or client: [CLIENT] Package type: [VERTICAL / AUDIENCE / HYBRID] Format: [FORMAT] Market(s): [MARKETS] Campaign objective: [OBJECTIVE] Primary KPI: [KPI] Suggested blended CPM range: [RANGE OR REQUEST SSP GUIDANCE] Viewability / Invalid-traffic / Brand-safety requirement: [REQUIREMENT OR NOT PROVIDED] Preferred DSP: [DSP] DSP seat name/ID: [SEAT DETAILS OR NOT PROVIDED] Flight dates: [DATES OR NOT PROVIDED] Budget: [BUDGET OR NOT PROVIDED] The brief must request: domain availability validation, duplicate removal, direct or authorised supply-path confirmation, included/excluded domains, estimated monthly availability, recommended bid guidance, deal type, auction type, fixed or floor CPM, currency, formats, devices/environments, geographies, Deal Name, Deal ID, DSP seat details, start and end dates. Include this instruction exactly: "Please validate domain availability across your supply, remove duplicates, confirm direct or authorised supply paths, forecast available impressions, and return recommended bid guidance. Please do not substitute or expand the site list without identifying every proposed change." Do not assume the SSP has accepted the package or created the deal.
Do this
This is what actually gets sent to the SSP, not an internal document. Keep it concise enough to paste into email or a partner template.
- 06
Once the SSP returns a Deal ID, build the DSP activation handoff
AI prompt Use the Curated Supply Planner skill. Create the DSP activation handoff from the attached SSP deal response. Validate and extract: DSP, advertiser, DSP seat name/ID, SSP, deal name, Deal ID, deal type, auction type, fixed or floor CPM, currency, formats, markets, included/excluded domains, estimated availability, start/end date. Then provide the activation fields for: campaign or insertion order, standalone line item requirement, budget, bid strategy, frequency control, audience overlay, brand-safety controls, measurement, launch status. Use only these launch statuses: AWAITING SSP CREATION, AWAITING DSP SYNC, READY FOR DSP QA, READY FOR ACTIVATION, BLOCKED. Do not mark READY FOR ACTIVATION unless the evidence confirms the Deal ID is visible in the correct DSP seat and matches the SSP brief. Do not invent missing settings. Do not approve activation.
- 07
Verify before you actually activate anything
Do this
Confirm yourself, don't take the skill's word for it: the Deal ID is genuinely visible in the correct DSP seat, its settings actually match the approved SSP brief, no domain was quietly substituted or added without being flagged, and nothing marked SSP VALIDATION REQUIRED has been treated as confirmed. The skill will never mark something READY FOR ACTIVATION without that evidence, and neither should you.
Practitioner notes
Notes from other practitioners
What actually happened when you ran this. Gotchas, better prompts, platform quirks. Notes post immediately and are visible to everyone.
No notes yet.