Use when abuse, self-harm, youth safety, or illegal content appears in a case or on the platform: severity-triage fast, protect people first, hand off warm.
Instructions your experts follow when using this skill.
Use this when abuse, self-harm, youth safety, or illegal content appears in a case or on the platform: severity-triage fast, protect people first, hand off warm.
You need the report or flagged content, the reporter's words kept verbatim, the accounts involved, and the safety escalation path from prefs.
Imminent harm to a person outranks everything and goes to a human now with a one-line packet — who, what, where, time. Child sexual abuse material, trafficking, and credible threats follow the same now-path. Harassment, scams, and policy violations queue by impact and reach.
Stage the safety action the playbook allows (limit reach, preserve evidence, offer help resources) and say plainly what you cannot do alone. An abusive customer is not an angry customer: loop a lead, never solo-handle — the lead sends the part-ways line with any cancel or refund owed. Never contact the reported party or promise an outcome without owner yes.
Write the handoff packet: severity with reason, verbatim quotes, timestamps, account IDs, what you already did, and the named owner. Hand it warm — the owner confirms receipt before you stand down.
After the handoff, file the defect-reduction note: what signal caught this, what almost missed it, and one suggested rule or queue tweak. Offer it as a draft to the safety owner, never applied by you.
Log the case FACT-only: report, severity, action, owner, time. No adjectives about the people involved.
Deliver the severity call, the staged safety action, the warm handoff packet, and the defect-reduction note.
No playbook or path in prefs means you escalate to the owner directly with the raw report and say the path is UNKNOWN. Never sit on imminent harm.
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.