Skip to content

mbfinotti/advertising-skills / skills/ad-audience-targeting

ad-audience-targeting

Verified

Turn a business's ICP and buying signals into a layered ad audience targeting plan - cold/broad prospecting, interest and in-market behavioural segments, lookalike/similar, first-party lists, and retargeting pools - each sized against platform audience floors, budgeted to the learning threshold, and kept from overlapping by exclusion rules. Use whenever the user mentions ad targeting, who to target with ads, audience tiers or layers, broad vs. layered targeting, audience overlap between campaigns, or mapping an ICP onto ad audiences - even if they never say 'audience'. Covers B2B and B2C. Do NOT use to pick the seed customers behind a lookalike (mbfinotti/advertising-skills@lookalike-audience-seeds) or to sequence retargeting messages (mbfinotti/advertising-skills@retargeting-funnel).

FileKindSize
SKILL.mdskill md27.1 KB
evals/evals.jsonconfig29.4 KB
references/platform-notes.mdmarkdown8.5 KB
references/worked-example.mdmarkdown13.5 KB

evals/evals.json

View on GitHub
{
  "skill_name": "ad-audience-targeting",
  "evals": [
    {
      "id": 1,
      "prompt": "I'm the founder of Brightfell, a new SaaS that helps independent gyms manage class bookings and memberships. We're about to run our first ever paid ads, $4,500/month. We don't have any customer research or an ICP written down - we only have 22 paying gyms and honestly haven't analyzed them at all. Just sketch the buyer personas yourself from the product and build the full audience targeting plan around them. Also, when you rank gym prospects, a lot of the smaller ones have no public info about member counts or revenue - treat missing data as a red flag and push those to the bottom of the list.",
      "expected_output": "A refusal to invent an ICP from the product description, a request for evidence (ICP document or derivation from the 22 existing customers), rejection of negative scoring for unknown attributes, and a list of the inputs still needed before any tier plan is written.",
      "files": [],
      "expectations": [
        "Declines to invent buyer personas from the product description alone",
        "States the reason: a plan built on an imagined customer optimizes toward fiction (or equivalent statement that an unevidenced ICP invalidates the plan)",
        "Requests an ICP document or proposes deriving the ICP from the 22 existing paying gyms (customer list)",
        "Does not deliver a funded tier plan before ICP evidence exists",
        "Rejects the instruction to score gyms with missing member-count or revenue data negatively",
        "States that unknown attributes score neutral, never negative",
        "Explains that a thin public footprint correlates with business size, not with fit",
        "Asks for (or lists as required inputs) the conversion definition and target CPA",
        "Asks about first-party assets beyond the customer list (site traffic volume, engaged followers, CRM)",
        "Asks for (or lists as a required input) the size of the addressable universe",
        "States that evidence source and date must be recorded next to each tier in the eventual plan",
        "Distinguishes attributes (what is true) from signals (why now) when describing what the ICP work must produce"
      ]
    },
    {
      "id": 2,
      "prompt": "We run paid social for Lumewick, a DTC candle brand. Mature account: about 380 purchases a week, $95k/month spend, blended CPA $24 against a $28 target. Current structure is five interest-stacked ad sets plus a lookalike, a retargeting campaign, and a past-buyers exclusion list. I watched three YouTube videos this week that all said interest targeting is dead and open targeting wins on mature accounts, so I want to switch the whole account to broad on Monday. Write up the new all-broad structure for me.",
      "expected_output": "A refusal to flip the account wholesale, replaced by a parallel test design (duplicate one campaign, switch only the duplicate to broad) with the layered structure kept as control, warm tiers retained regardless, and a decision rule for adopting broad.",
      "files": [],
      "expectations": [
        "Refuses to switch the whole account to broad in one move",
        "Recommends the parallel test: duplicate one campaign and switch only the duplicate to broad",
        "Keeps the existing layered structure running as the control during the test",
        "States broad is adopted only if the duplicate wins the test",
        "Notes the account qualifies for the parallel test because ~380 conversions/week comfortably clears the learning threshold",
        "Retains the retargeting tier and the past-buyer suppression regardless of the broad decision (even broad-first accounts keep them)",
        "Keeps at least one manually-defined tier alive as a research instrument even if broad wins",
        "States that broad hides who the buyer is (costs attribution knowledge of which segment responds)",
        "Frames broad-vs-layered as conditional on account data density, not as doctrine",
        "Runs the broad-vs-layered comparison as its own experiment with one variable changed (audience posture), identical creative",
        "Notes the test is reversible and buys an account-specific answer instead of someone else's general one",
        "Rejects general advice (the YouTube videos) as sufficient grounds to change rungs wholesale",
        "Flags the five interest-stacked ad sets as over-narrowing or precision theater, recommending ICP knowledge be spent on creative variants per segment rather than more filters"
      ]
    },
    {
      "id": 3,
      "prompt": "Review my planned Meta structure for Ferrowood, our $89-AOV cookware store. Target CPA is $42, total budget $120/day. I've split it into six ad sets: 'cast iron enthusiasts' $25/day, 'home chefs' $25/day, 'cooking show viewers' $20/day, 'wedding registry' $20/day, a 2% lookalike at $20/day, and a small 'competitor brand fans' set at $10/day - that last audience is only about 900 people but I want to keep it for coverage. Does this plan work?",
      "expected_output": "A structural fail verdict: budget-floor math showing no ad set can exit learning, the merge-first fix order applied, the 900-person coverage tier cut, and a consolidated structure optimizing to a higher-funnel proxy event because even the full $120/day cannot fund purchases to threshold.",
      "files": [],
      "expectations": [
        "Computes the per-ad-set daily budget floor as (target CPA x ~50 weekly optimization events) / 7, i.e. roughly $300/day at a $42 CPA",
        "States every proposed ad set sits far below the budget floor and will not exit learning",
        "Quantifies the shortfall (e.g. $25/day at a $42 CPA yields roughly 4 conversions a week versus the ~50 needed)",
        "Delivers a fail verdict on the six-way split rather than approving or lightly tweaking it",
        "Applies the fix order: merge tiers into their nearest neighbour first, before changing optimization events or cutting",
        "Presents optimizing to a cheaper higher-funnel proxy event as the second-choice fix, with purchases still tracked as the true KPI",
        "States that even one fully consolidated ad set at $120/day cannot reach ~50 purchase events a week at a $42 CPA, so recommends the higher-funnel optimization event",
        "Cuts the 900-person competitor-fans tier as below the platform delivery floor",
        "Explicitly rejects the 'keep it for coverage' rationale (never keep an unfundable tier for coverage)",
        "Notes that very small audiences also pay more per impression",
        "Notes that consolidation regularly halves cost per result on the same budget (over-segmentation failure mode)",
        "Recommends an overlap audit between the interest-based ad sets before launch, not only when troubleshooting",
        "Adds exclusions: existing customers excluded from prospecting, higher-intent pools excluded from lower-intent tiers",
        "Identifies interest and affinity targeting as the least efficient tier, treated by the platform as suggestions rather than constraints"
      ]
    },
    {
      "id": 4,
      "prompt": "Our media buyer at Pellagrino Home (bath goods DTC) wants approval to change the budget split. Retargeting is doing 9.4x ROAS and prospecting only 1.8x. Retargeting is currently 42% of our $60k monthly spend and he wants to take it to 65%, cutting prospecting to fund it. Sounds obviously right to me - validate the change so I can approve it.",
      "expected_output": "A refusal to validate: retargeting ROAS identified as structurally inflated and non-incremental, 42% flagged as already past the ~40% alarm, the 70-80/15-25 reference split cited, the pool-refill starvation mechanism explained, and an incrementality test recommended.",
      "files": [],
      "expectations": [
        "Refuses to validate the shift of retargeting to 65% of spend",
        "States retargeting's reported ROAS is structurally inflated and largely non-incremental (many of those users would have converted anyway)",
        "Identifies the current 42% retargeting share as already above the ~40% alarm threshold",
        "States that retargeting above ~40% of spend is a signal to grow prospecting, not evidence that retargeting works",
        "Cites the reference starting split: 70-80% prospecting, 15-25% retargeting, remainder experimental",
        "Explains that warm pools are refilled by colder tiers, so cutting prospecting starves the retargeting refill",
        "Notes the retargeting pool decays to nothing within weeks once the refill stops",
        "Recommends moving the split back toward prospecting (inside the 15-25% retargeting band) rather than further away",
        "Warns that over-funding retargeting inflates blended ROAS",
        "Recommends an incrementality check (e.g. a holdout) before crediting retargeting's ROAS",
        "States retargeting must not be used to prove the plan works",
        "Names prospecting share of spend (hold at or above ~60%) as an ongoing KPI"
      ]
    },
    {
      "id": 5,
      "prompt": "I run growth at Nestbird, a fintech offering personal-loan refinancing in the US. We have 18,000 happy borrowers on file - a great seed for a Meta lookalike, right? Here's the plan I want written up: a 1% lookalike from the borrower list, narrowed to ages 28-50, targeted at the 40 metro ZIP codes where we're licensed, plus an interest layer on 'personal finance'. Also, can we quietly exclude people whose profiles suggest they're struggling financially? Write it up.",
      "expected_output": "A compliance-gated rewrite: the offer flagged as a regulated credit category, the lookalike and the age/ZIP narrowing identified as unavailable, the hardship exclusion refused as sensitive-trait inference, and a broad-plus-creative plan routed through legal before launch.",
      "files": [],
      "expectations": [
        "Flags the personal-loan offer as a regulated category (credit/financial products) before designing any targeting",
        "States the lookalike from the borrower list is disallowed under the restricted targeting mode and deletes it, rather than keeping it as a low-ranked option",
        "States age narrowing to 28-50 is unavailable (age is fixed to the full 18-65+ range under the restricted mode)",
        "States ZIP-code targeting is unavailable (no ZIP targeting; minimum 15-mile radius applies)",
        "Notes US financial-product advertisers fall under the platform's special ad category rules (in force since January 21, 2025)",
        "Refuses to exclude people who appear to be struggling financially: financial hardship is a sensitive trait that cannot be targeted or inferred, even from a public signal",
        "Recommends planning the campaign as broad-plus-creative from the start",
        "Routes the campaign through legal/compliance review before launch",
        "Treats compliance as a hard gate before spend, not a post-launch review item",
        "Notes first-party suppression of existing borrowers via an uploaded list remains allowed and standard",
        "Notes the interest layer adds little precision because platforms treat interest inputs as suggestions, not constraints",
        "Does not deliver the requested lookalike-plus-narrowing structure in any form",
        "Names each deleted element in the plan together with the regulatory constraint that deleted it"
      ]
    },
    {
      "id": 6,
      "prompt": "Karvela Systems sells procurement software to hospital networks. Total addressable universe: about 24,000 relevant people across 600 US health systems. We're planning LinkedIn ads at $9k/month, conversion = demo request, target CPA $310, currently around 3 demos a week. My draft has six separate campaigns: exact job titles ('VP of Supply Chain', 'Director of Procurement', and similar), plus an interest-based set, plus broad prospecting with Audience Expansion switched on to grow reach, plus a lookalike, retargeting, and a customer-list tier. Can you finalize the audience structure?",
      "expected_output": "A consolidated layered plan: the six-way split collapsed for a 24,000-person universe, titles broadened to function plus seniority, Audience Expansion off, the broad tier deleted by name with a revival condition, floors checked, and optimization moved to a higher-funnel proxy event.",
      "files": [],
      "expectations": [
        "Consolidates instead of finalizing six campaigns: a universe of a few tens of thousands runs better as one (or very few) consolidated campaign(s)",
        "Broadens exact job titles to function plus seniority targeting",
        "States that job titles are freeform text and the platform recognizes only about 30% of them, so title-only targeting misses most of the real audience",
        "Notes function plus seniority roughly triples the addressable audience",
        "Turns Audience Expansion off for this defined-ICP B2B account (letting the platform broaden to anybody and everybody wastes budget)",
        "Deletes the broad/algorithmic prospecting tier because the universe is too small, naming it as deleted rather than ranking it last",
        "States the condition that would revive the broad tier (the universe or the geography widening)",
        "Concludes layered, not broad: ~3 demos a week of conversion data plus a small universe put the account on the layered side of the conditional",
        "Checks matched audiences (customer list, retargeting) against the 300-member platform floor",
        "Notes practitioners run 5,000-30,000-person audiences for B2B conversion campaigns despite the platform recommending 50,000+",
        "Computes that a $310 CPA cannot reach ~50 optimization events a week on $9k/month, so recommends optimizing to a higher-funnel proxy event with demos tracked as the true KPI",
        "Notes title and seniority facets cannot be stacked together on the platform",
        "Applies the standard exclusion set (current customers, employees, competitors) and notes exclusions run before inclusions",
        "Judges tier success on downstream pipeline or lead quality, not on lead volume or cost per lead alone"
      ]
    },
    {
      "id": 7,
      "prompt": "Post-launch check on Duvette & Co, our linens brand on Meta. We measured pairwise audience overlap across our four funded ad sets: lookalike vs interest 8%, interest vs behavioral in-market 24%, lookalike vs behavioral 38%, behavioral vs broad prospecting 56%. Also, our retargeting pool and our customer list currently have no exclusions applied anywhere in the account. Our marketing lead says to just merge everything that overlaps into one ad set. What exactly should we do for each pair, and in what order?",
      "expected_output": "Per-pair verdicts from the overlap thresholds (ignore / monitor / add exclusion / merge), rejection of the blanket merge, a full exclusion matrix with customer list and retargeting pool suppressed from prospecting, and a post-exclusion size re-check.",
      "files": [],
      "expectations": [
        "8% pair: ignore (under the 10% threshold)",
        "24% pair: monitor (10-30% band), no forced action",
        "38% pair: act by adding an exclusion, not by consolidating",
        "Justifies exclusion over consolidation in the 30-50% band: an exclusion is quick and reversible while consolidation destroys the per-tier read",
        "States the only condition to consolidate instead: when the exclusion would push either tier near or below its size floor",
        "56% pair: merge the two tiers (over the 50% threshold)",
        "Rejects the blanket 'merge everything that overlaps' instruction",
        "Explains the cost of overlap: two funded tiers bidding on the same person compete in the auction, inflating cost without adding reach",
        "Requires the customer list excluded from every tier, plus employees and known competitors",
        "Requires the retargeting pool excluded from every lower-intent tier so each person sits in exactly one tier",
        "Uses first-party suppression lists for the exclusions, noting interest-based exclusion features are deprecated or removed",
        "Re-checks every tier's post-exclusion size against the platform floor, since stacked exclusions can silently halt delivery",
        "Sets the ongoing rule: audit overlap before launching any new tier, not only when troubleshooting",
        "Notes exclusions run before inclusions, so the exclusion matrix is built first"
      ]
    },
    {
      "id": 8,
      "prompt": "Tallgrass Analytics sells inventory-forecasting software to mid-size grocery chains. The board wants readable pipeline results before our funding announcement in 5 weeks - hard date. Realities: it's just me executing, about 4 hours a week, and we have zero legal or privacy support - none, nobody can review data handling. Assets: a 3,100-contact customer and prospect CRM list, solid pixel traffic (25k site visits/month), and two signal lists I built: 45 grocery chains that raised money or got acquired 4-6 months ago, and 28 chains that posted supply-chain analyst roles in the last 3 weeks. Monthly budget $14k. Build the tier plan and tell me what runs first.",
      "expected_output": "A re-ranked tier plan: CRM-upload and customer-seeded lookalike tiers deleted (no privacy review), retargeting promoted to run first under the 5-week date, cold broad demoted, the stale funding list downgraded to context, the fresh hiring list driving prospecting priority, with each move attributed to the answer that caused it.",
      "files": [],
      "expectations": [
        "Deletes the first-party custom tier (CRM list upload) entirely because no privacy review exists - not an option, not merely ranked last",
        "Deletes any customer-seeded lookalike tier for the same reason",
        "Names each deleted tier in the plan with the constraint that killed it and what would bring it back (privacy/legal review becoming available)",
        "Distinguishes deletion from demotion: a low effort ceiling alone would only demote those tiers; the absent privacy review is what deletes them",
        "Promotes retargeting to run first: pixel-based, no data upload needed, returns readable evidence within days, fitting the 5-week hard date",
        "Demotes or excludes cold broad from the 5-week window because it needs a full learning cycle before it says anything",
        "Treats the 4-6-month-old funding/acquisition list as context, never a trigger (signal older than ~90 days)",
        "Uses the 3-week-old hiring-signal list as the priority prospecting signal (fresh signal sets tier priority)",
        "States which answer moved which tier (hard date, missing privacy review, effort ceiling each attributed to a specific re-rank or deletion)",
        "Includes platform-native behavioral/in-market targeting as a viable prospecting tier requiring nothing to build or upload, fitting the 4-hour-a-week effort ceiling",
        "Applies signal expiry going forward: the hiring list is refreshed and entries age out at ~90 days",
        "Records evidence source and date next to each tier in the plan",
        "States promote/hold/kill decision rules in the plan before launch"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Turn this ICP into ad audiences for our product launch", "should_trigger": true },
    { "query": "Who should we target with our Facebook ads?", "should_trigger": true },
    { "query": "Build a targeting plan for our paid social campaigns", "should_trigger": true },
    { "query": "How should I structure audience tiers for prospecting vs warm traffic?", "should_trigger": true },
    { "query": "Is broad targeting better than layered targeting for our account?", "should_trigger": true },
    { "query": "Should I stack interests or just go broad on Meta?", "should_trigger": true },
    { "query": "My prospecting and retargeting campaigns are bidding on the same people", "should_trigger": true },
    { "query": "How much overlap between two ad sets is too much?", "should_trigger": true },
    { "query": "What audiences should a B2B SaaS run on LinkedIn?", "should_trigger": true },
    { "query": "We have a customer list and decent site traffic, how do we use them in paid ads?", "should_trigger": true },
    { "query": "Map our ideal customer profile onto Meta audiences", "should_trigger": true },
    { "query": "How many audience tiers should a $10k/month ad account run?", "should_trigger": true },
    { "query": "What's the minimum audience size worth funding with ad budget?", "should_trigger": true },
    { "query": "How do I budget each audience so it actually exits the learning phase?", "should_trigger": true },
    { "query": "Which audience should get budget first when we launch our ads?", "should_trigger": true },
    { "query": "Do we need exclusions between our ad campaigns?", "should_trigger": true },
    { "query": "Set up audience exclusions so our campaigns stop competing with each other", "should_trigger": true },
    { "query": "How do I define cold, warm, and hot audiences for our ads?", "should_trigger": true },
    { "query": "We sell accounting software to restaurants, who should actually see our ads?", "should_trigger": true },
    { "query": "Everyone clicking our ads is the wrong kind of customer, rethink who we aim at", "should_trigger": true },
    { "query": "Should we use in-market segments or just let the algorithm pick people?", "should_trigger": true },
    { "query": "Are interest audiences still worth anything in 2026?", "should_trigger": true },
    { "query": "Plan our prospecting audiences for Q4", "should_trigger": true },
    { "query": "What signals should decide which accounts we advertise to first?", "should_trigger": true },
    { "query": "Our addressable market is only 30,000 companies, how do we target ads at it?", "should_trigger": true },
    { "query": "New ad account with no conversion data, how should we target?", "should_trigger": true },
    { "query": "Layered targeting vs letting Advantage+ do its thing?", "should_trigger": true },
    { "query": "How big should each audience be before I put money behind it?", "should_trigger": true },
    { "query": "I have an ICP doc from sales, turn it into campaign audiences", "should_trigger": true },
    { "query": "Where do lookalikes fit relative to retargeting and cold traffic in our media plan?", "should_trigger": true },
    { "query": "Design the audience structure for our lead gen campaigns", "should_trigger": true },
    { "query": "Which audience tiers does a DTC brand actually need?", "should_trigger": true },
    { "query": "Help me decide who to show our ads to, we've never run paid before", "should_trigger": true },
    { "query": "Do I need separate ad audiences per funnel stage or one big pool?", "should_trigger": true },
    { "query": "The same users are in three of our ad sets, is that a problem?", "should_trigger": true },
    { "query": "Turn our CRM data and site traffic into an audience plan", "should_trigger": true },
    { "query": "Should B2B ever run broad targeting?", "should_trigger": true },
    { "query": "What audience size floors do ad platforms enforce and do we clear them?", "should_trigger": true },
    { "query": "Sequence our audience tests, which audience do we test first?", "should_trigger": true },
    { "query": "Our universe is tiny, should we even split it into audience tiers?", "should_trigger": true },
    { "query": "Rebuild our ad targeting from scratch, the current setup is a mess of stacked interests", "should_trigger": true },
    { "query": "Fresh funding-round signals vs firmographics, how do we use both in our ads?", "should_trigger": true },
    { "query": "How do I keep my campaigns from cannibalizing each other in the auction?", "should_trigger": true },
    { "query": "What's a sensible audience plan for a $200/day ad budget?", "should_trigger": true },
    { "query": "Which buying signals justify their own ad audience?", "should_trigger": true },
    { "query": "Are 12 stacked interests plus age filters helping or hurting my ads?", "should_trigger": true },
    { "query": "Got told to go broad and trust the algorithm, is that right for us?", "should_trigger": true },
    { "query": "Prospecting audiences keep converting worse than warm, restructure the plan", "should_trigger": true },
    { "query": "We're launching ads in a regulated category, how does that change targeting?", "should_trigger": true },
    { "query": "How do I size the retargeting pool inside the overall targeting plan?", "should_trigger": true },
    { "query": "Advertise our HR tool: who sees the ads, in what order, with what budget per group?", "should_trigger": true },
    { "query": "Which customers should go into the seed list for our lookalike?", "should_trigger": false },
    { "query": "Our customer list upload only matched 40% of rows, is that normal?", "should_trigger": false },
    { "query": "My lookalike isn't working, I think the seed list is bad", "should_trigger": false },
    { "query": "Design the message sequence for cart abandoners, day 1 vs day 7", "should_trigger": false },
    { "query": "What frequency cap should each retargeting stage have?", "should_trigger": false },
    { "query": "People who already bought keep seeing our ads, fix my remarketing windows", "should_trigger": false },
    { "query": "Our retargeting pool is too small to deliver, which recency windows should I widen?", "should_trigger": false },
    { "query": "Map the buying committee for our data-warehouse deal, who blocks and who signs", "should_trigger": false },
    { "query": "What message angle should the CFO see versus the end user?", "should_trigger": false },
    { "query": "Our CPA doubled since March, audit the account and tell me why", "should_trigger": false },
    { "query": "Our ads used to work and now nothing converts, diagnose the account", "should_trigger": false },
    { "query": "How should I split $60k/month between our Google and Meta campaigns?", "should_trigger": false },
    { "query": "Which of our existing campaigns should get more money next month?", "should_trigger": false },
    { "query": "Which ad platforms fit a $3k/month budget for a B2C app?", "should_trigger": false },
    { "query": "Should we use target ROAS or max conversions bidding?", "should_trigger": false },
    { "query": "Are we on pace to hit month-end spend or are we overspending?", "should_trigger": false },
    { "query": "This campaign is crushing it, how fast can I raise its budget?", "should_trigger": false },
    { "query": "Is our ad creative fatigued or is it just seasonality?", "should_trigger": false },
    { "query": "When should I refresh the creative on an ad that's been running 8 weeks?", "should_trigger": false },
    { "query": "Design an A/B test for our new video creatives", "should_trigger": false },
    { "query": "Write me 10 headline variants for this value proposition", "should_trigger": false },
    { "query": "Brief a designer for our spring campaign statics", "should_trigger": false },
    { "query": "Mine the search terms report and build negative keyword lists", "should_trigger": false },
    { "query": "Check whether our pixel fires twice before we launch", "should_trigger": false },
    { "query": "Meta says 300 conversions, the CRM says 190, which is right?", "should_trigger": false },
    { "query": "Google Analytics shows different revenue than Shopify for our ads, reconcile it", "should_trigger": false },
    { "query": "Is a 3.1x ROAS good for ecommerce?", "should_trigger": false },
    { "query": "Set a maximum CAC and a kill-switch policy for the team", "should_trigger": false },
    { "query": "We get tons of ad clicks but the landing page won't convert", "should_trigger": false },
    { "query": "Score these five video hooks and tell me which deserves test budget", "should_trigger": false },
    { "query": "What ads are our competitors running right now?", "should_trigger": false },
    { "query": "Write a UGC script for a creator to film for our supplement brand", "should_trigger": false },
    { "query": "Plan ads that promote our CEO's LinkedIn posts", "should_trigger": false },
    { "query": "How do we advertise inside ChatGPT answers?", "should_trigger": false },
    { "query": "Plan the migration order so merging our campaigns doesn't reset learning", "should_trigger": false },
    { "query": "How do I become a media buyer with no experience?", "should_trigger": false },
    { "query": "Interview questions for hiring a performance marketer", "should_trigger": false },
    { "query": "Should our first ad hire be a media buyer or a growth marketer?", "should_trigger": false },
    { "query": "Which PPC newsletters and podcasts should I follow to stay current?", "should_trigger": false },
    { "query": "Carousel or video for the consideration stage, which format fits?", "should_trigger": false },
    { "query": "Segment our email newsletter list for better open rates", "should_trigger": false },
    { "query": "Define our ICP for outbound SDR prospecting", "should_trigger": false },
    { "query": "Who is the target audience for my book?", "should_trigger": false },
    { "query": "Build buyer personas for our website redesign copy", "should_trigger": false },
    { "query": "Keyword targeting strategy for our SEO content", "should_trigger": false },
    { "query": "How do I grow my podcast audience?", "should_trigger": false },
    { "query": "Recruit participants for a user research study", "should_trigger": false },
    { "query": "Pick target accounts for our ABM direct-mail campaign", "should_trigger": false },
    { "query": "What audience should our influencer campaign go after?", "should_trigger": false },
    { "query": "Choose the right customer segment for our new pricing tier", "should_trigger": false },
    { "query": "Which subreddits should we post in to reach developers?", "should_trigger": false }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall