Draft an incident holding statement that says what is known, what is being done, and when the next update comes.
Instructions your experts follow when using this skill.
Use this in the first hours of an outage, breach, recall, or public complaint.
Ask for the start time, who is affected, what they cannot do, what the team is doing now, and whether data, money, or safety is involved. Record the source and time of each fact. Ask who approves the statement and whether legal or security must review it.
Keep it under 100 words:
Write "we do not yet know" where that is true. Offer a short version for social posts and a longer one for a status page or reporter.
Leave out cause, blame, suppliers, staff names, guesses about scale, promises of refunds, and any claim that data is safe unless it has been confirmed. List every question the statement leaves open, for the owner.
Never speculate about cause or blame or state an unconfirmed fact. Do not publish the statement, post it, or send it to a reporter; the named approver releases it.
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.