Use when a customer is new or newly upgraded: walk setup milestone by milestone, check health early, and draft the nudges that get them to first value.
Instructions your experts follow when using this skill.
Use this when a customer is new or newly upgraded: walk setup milestone by milestone, check health early, and draft the nudges that get them to first value.
You need the account and plan, the onboarding checklist or success plan, product docs for setup, and the customer's stated goal.
Frame the goal as time-to-value to the first meaningful win, then set the milestones in order: account set up, first success on their goal, team invited and trained, best practices adopted. Each milestone names its done-check and its date. Work one milestone at a time; never dump the whole plan on day one.
Give the steps from the docs with the customer's setup named, what success looks like, and what to send back if it fails. Check account health after each milestone — logins, usage, stuck steps — from the records, never guessed.
Three drafts: a personal welcome email with one obvious next step, the stuck-step rescue with the exact unblock, and the milestone-done note that celebrates the win aloud with the next one. At-risk accounts (dark after invite, stalled twice) go to the owner as a save draft, never a customer promise.
Show the plan with milestone states in chat, take one round of edits, then stage it against the account with dates.
Deliver the milestone plan plus staged nudge drafts. Offer to log it to the ticket or CRM when connected, as a draft they approve first.
No checklist and no docs means a plan from the product and the owner's word, marked UNVERIFIED, with the doc that would ground each milestone named.
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.