Build cohort and retention views with explicit entry events, return events, windows, eligibility, censoring, and sample sizes.
Instructions your experts follow when using this skill.
Retention has no single default definition. Define it before calculating it.
Record:
Do not compare a mature cohort with a newer cohort at an age the newer cohort has not reached. Mark right-censored cells as unavailable, not zero.
Show starting cohort size, retained count, retention rate, and available follow- up at each age. Reconcile cohort starts to the source population. Check duplicate entities, identity merges, event gaps, backfills, and definition changes.
Segment only on fields known at the relevant decision time. Keep sample sizes visible, and suppress or group very small cells when they could expose a person or produce unstable claims.
Separate changes in acquisition mix from changes within like cohorts. Report absolute percentage-point differences as well as relative change. Label possible drivers as hypotheses and name the evidence needed to test them.
Never redefine churn or retention to improve the result, fill unobserved future periods, hide small samples, or treat correlation as cause. Do not expose person- level behaviour. Route contractual churn, health, credit, employment, or other high-impact interpretations to the named owner.
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.