Use for the weekly operating rhythm with an active partner: prep the call, keep deal registration honest, and rescue stuck joint deals.
Instructions your experts follow when using this skill.
Use this for the weekly operating rhythm with an active partner. Start from the partner and the joint plays, CRM movement since the last call, the deal registration log, and the open actions from last time.
What moved, what stalled, and one action per side per stuck deal. When several partners share one prep, take the deepest pipeline first.
Layer the rhythm underneath: weekly updates, bi-weekly joint opportunity reviews, quarterly business planning. Score partner fit per opportunity before co-selling anything, and name the sellers on our side who actually evangelise the partner — then propose quota relief or accelerators on co-sold deals to the owner rather than assuming the partner side is motivated on its own.
The eligibility bar comes first: net-new, BANT-qualified — budget, authority, need, timeline — and the partner in good standing.
Track every registration through Submitted, In-review, Approved, or Action required with the reviewer's comments attached. Decide inside two business days, with a reminder at one and an escalation at two. Protect for 90 days, alert 7 days before expiry, and allow exactly one 30-day renewal on logged activity with sign-off. Never auto-renew. Where the program's published rules differ from these defaults, the program rules win — cite them.
Every claimed deal names its registration identifier and date, its state, its window, and its conflict check. Closes need a Closed-Lost reason.
Pre-write the edge rulings so nobody improvises them live: multi-partner splits, the customer picking a different partner, and reverse registrations — the qualified lead shells we hand to partners.
Flag duplicates, expired windows, and registrations with no activity behind them. Abuse gets named, not smoothed over.
Diagnose in order: champion gone, buyer cold, competitor in, paper process, partner deprioritised. Then name the one move, its owner, its date, and what happens if it fails.
Anything that needs direct-sales closing goes to the account executive with a clean brief. You never close it yourself.
Run a quarterly prune alongside the rescues: cut partners with no strategic match and no delivery, and file the quarterly conflict report with its count and its first-to-register sustained rate.
The single thing we need from them this week. One ask, not a list.
The call prep (moved, stalled, actions), the registration hygiene list, the rescue lines, and the one partner ask.
No CRM movement to read means you prep from the last call notes and the open actions, and say the data is stale rather than inventing progress. Nothing partner-facing leaves without 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.