Use when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone: the CI brief with landscape, change blocks, pricing read, and win strategy.
Instructions your experts follow when using this skill.
Use this when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone. Start from the competitors, what your product sells, and the decision the read informs. Gong call excerpts and win-loss notes, where they exist, are the quotes the win strategy rests on.
Tier 1 direct competitors for a deep read, Tier 2 adjacent substitutes for a skim, Tier 3 aspirational for a monthly read. Each gets its pricing, changelog, product, and careers pages logged — including fetches that fail — plus review-site mining, competitor demo notes, and community chatter where they exist.
Group the changes by competitor and cite the link and date on each line. Keep to moves that matter: launches, pricing, messaging, positioning shifts. A competitor with nothing worth reporting is left out entirely, and an unlinked claim never makes the page.
Two to four lines per material move, for this user's GTM job. A launch gets a positioning read, a pricing move gets a packaging read, a content push gets an enablement read. Say it is unclear when it is unclear.
Three discriminators with proof, the competitor line the rep will hear, and the counter in rep register. Fold in win-loss quotes where they exist, quoted not paraphrased.
One page per competitor, scannable in under two minutes. Each card carries win/loss zones (where you win, where you battle, where you lose), the Know/Say/Show for the rep's exact words, scenario variants for head-to-head versus rip-and-replace (the pain of staying must outweigh the pain of switching), and a 90-day deal-intel pane with the latest win, loss, and at-risk quotes. Refresh on signal, never on schedule alone — changelog, pricing, review batches, exec changes, and earnings trigger a same-week versioned diff — with a biweekly floor for Tier 1 cards. Every card names its owner, last refresh, and approver; a card with no owner is retired until it has one.
The brief, saved dated with sources and a full source ledger including failures. A quiet market is one line saying so, not a brief. Never brief the same change twice — fold in what the routine already logged.
No competitor list means you draft the watch list from the market and ask for a yes. No pricing pages means you say so and refuse the pricing read. Never pad the brief to look busy, and never invent a competitor move, a price, or a customer. Battlecards publish rep-wide 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.