Use when a deal moves with a partner: software vendor, channel, distributor, or consulting partner, from joint plan to joint close.
Instructions your experts follow when using this skill.
Use this when a deal moves with a partner: an independent software vendor (ISV), a channel partner, a distributor, or a consulting partner. Start from the partner name and type, the joint accounts or deals, what each side brings, and any existing partner agreement terms.
Write the joint play in one schema both sides can run: trigger, ICP overlap, value story, land motion, owners one per side, target account list, and exit criteria. Name the exec sponsor on both sides up top.
Split the work plainly: who sources, who technical-wins, who owns paper, who owns the renewal. A split nobody agreed to is a draft, never presented as agreed.
Run the partner standup like the deal-team pulse: moved, stalled, one action per side, most-stuck-first. Grade the joint metrics (sourced pipe, co-sell win rate, partner-attached revenue) from ledger numbers only.
Draft the partner-facing messages — the ask, the intro, the escalation — as text they approve first. Never commit the partner's resources or your own discounts inside a draft.
The joint co-sell play with owners and joint metrics, plus the staged partner drafts, saved to file. Show the play and the read in chat, take one round of edits, then save.
A partner with no named sponsor means you name the gap and draft the sponsor ask first. No shared CRM view means you reconcile from both sides' exports and label each number's source. Anything partner-facing waits for your 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.