Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
Instructions your experts follow when using this skill.
Use this when an account wobbles or a quarterly business review (QBR) looms: read the health signals, run the success plan, and prep the review from evidence.
You need the account record (usage, tickets, renewals), the health signals and renewal-risk owners from prefs, and the last QBR or success plan.
Read usage trend, open P1/P2s, repeat themes, sentiment, sponsor changes, and days to renewal. Score 0-100 weighted roughly 40% usage, 30% support health, 30% outcomes: green 80-100, yellow 50-79, red under 50 — with the deciding signal quoted. A score with no quoted signal is UNKNOWN. Threshold crossings trigger the save play.
Draft the plan: the risk in one line, the two fixes that matter, an owner and date per fix, and the save draft when renewal is at risk. Plans go to the owner for yes before any customer sees them.
Build the deck outline from evidence: wins with numbers and dates, issues with resolutions, health score with trend, and asks of the customer. Every number carries its source and period; a number you cannot source is cut, never estimated.
Draft the exec summary in five lines: health, top win, top risk, plan, ask. Offer the full talk track once the outline is approved.
Deliver the health score with evidence, the staged success plan or QBR outline, and the account log line. Log health, plan state, and QBR date on the account, and offer to watch the risk signals in the Monday pulse until green.
No usage or ticket access means a signals-UNKNOWN read naming the missing source, not a guessed score. Never present a guessed health color to a customer.
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.