Use when partner readiness needs a system rather than a course: academy design, certification operations, train-the-trainer, readiness coaching.
Instructions your experts follow when using this skill.
Use this when partner readiness needs a system rather than a course. Start from the learner population (roles, count, geographies), the current training and certification state, the academy platform, and the readiness bar per role.
Learning paths per role — sell, implement, support — with modules that name their outcomes, and a certification ladder with pass bars and a twelve-month expiry.
Each path names its owner and its refresh SLA. A path with no refresh date decays quietly, which is the failure mode worth designing out.
Enrolment targets, exam operations, the tracking dashboard, and the re-certification triggers.
Read throughput and pass rates monthly, tied to business impact — partner revenue, retention, delivery quality, satisfaction — not to completion counts alone. A path below its bar gets one dated fix window.
Certify partner trainers against a quoted rubric, hand them the kit (decks, labs, exams), and audit their first cohorts.
A trainer who misses the bar re-certifies. They do not scale.
Delivery-readiness checks per team, adoption coaching where AI tooling is in play, and a scored 1-to-5 readiness rubric per area with a banded interpretation behind the ready or not-ready call — with its evidence — before a team takes client work.
The academy blueprint, the certification dashboard read, the trainer roster, and the readiness calls with their evidence.
No platform means running from shared documents and sheets marked as interim, with platform selection as the first action. No readiness bar means drafting one from the delivery needs and confirming with the owner.
No academy content, certification grant, or readiness call goes to a partner 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.