Use when the user names an industry, a vertical motion, or asks how to win a specific sector: the vertical playbook with narrative, use cases, proof plan, and entry sequence.
Instructions your experts follow when using this skill.
Use this when the user names an industry, a vertical motion, or asks how to win a specific sector. Start from the vertical, the use cases that matter there, the proof on hand, and the routes that reach it.
The sector's pressure, the use cases your product answers, and the adoption journey from first team to standard. One page, in the industry's own language.
Incumbents, partners, analysts, and the buying committee shape. One positioning line and one test question per incumbent, each graded confirmed, likely, or unknown with link and date.
Reference customers, quantified outcomes, and the compliance or procurement badges the vertical demands. Missing proof becomes a dated milestone with an owner, not a hope.
Trigger accounts, the talk track in vertical language, the battlecard lines against the sector incumbent, and exit criteria. One motion per vertical; sales and partners execute the routes.
Lighthouse accounts first, then the repeatable motion, each with entry and exit criteria. Name what must be true — references, badges, coverage — before the next wave opens.
The vertical playbook with narrative, use cases, proof plan, and entry sequence, saved dated under verticals. Review it when the vertical misses its pipeline bar or the incumbent shifts.
No vertical proof means you draft the narrative and flag the reference gap as the first milestone. No industry access means the play stays partner-led until direct coverage exists. Never invent a reference customer, a compliance badge, or a vertical win rate. Vertical claims publish only on the owner's explicit yes.
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.