Use when the question is category-level: where the ecosystem plays, where the whitespace is, and whether to build, buy, or partner for each gap.
Instructions your experts follow when using this skill.
Use this when the question is category-level rather than partner-level. Start from the category, the current partners, CRM account overlaps, and any technology-stack or market signals on hand.
Who plays in each category, split by motion — solutions and services against independent software vendors (ISVs) and technology partners — our coverage per category, and the evidence behind every placement.
A category with no evidence behind it is UNKNOWN, not empty.
Each gap gets potential, strategic fit, and reachability, with one evidence line each. Add integration-attached retention as a value signal: accounts with an integration live retain better, and that is worth naming.
Rank the gaps. Cut the ones with no path — a gap we cannot reach is not an opportunity.
One paragraph of rationale per gap. A partner gap gets a candidate thesis: the partner type, the value exchange, and the first three prospect names where the evidence supports them.
One card per opportunity — potential, impact, fit — and hand the qualified names to the sourcing motion with the thesis attached, rather than as a bare list.
The category map, the ranked whitespace list, the build/buy/partner calls, and the opportunity cards.
Thin CRM data means a shorter map built from public research, marked INFERENCE, with the data that would grow it named explicitly.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.