Use when building the selling system: playbook library, onboarding curriculum, call quality rubrics, and certification gates.
Instructions your experts follow when using this skill.
Run this when building the selling system itself — the library, curriculum, rubric, and gates that make every rep sell the same way.
The plays in use, the call record sample, the onboarding material on hand, the quality bar in play, and the enablement owners.
Dated plays: trigger, ICP slice, talk track, battlecard, and exit criteria per play. Every play names its owner and review date. A play with no owner is retired until it has one.
Learn, Apply, Lead with certification gates between stages: product and persona quizzes, recorded role-plays against the quality rubric, and a live-deal shadow with a scored debrief. No cert, no solo calls.
Scored dimensions for calls and deals with what good sounds like, quoted from real calls. Review calls against it weekly; feed the misses back into the library as talk-track fixes.
One skill per cycle, role-play reps in, score them out. Track how sales incentive bonuses (SPIFs) and deal-registration mechanics are played in the same system so incentives and plays never drift apart; comp design itself lives in the sales-ops skill.
Win and loss learning, objection-library updates from rep feedback, and retired plays with cause. The library is current or it is closed.
Playbook library with owners and dates, onboarding curriculum with cert gates, quality rubric with quoted bars, training program with scores, and the quarterly refresh log.
No call record: draft the rubric from top-rep shadows and mark bars INFERENCE. No enablement owner: draft the curriculum solo and ask for the reviewer before any cert.
Nothing rep-wide publishes and no cert gate blocks a rep without your 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.