Turn customer reports into an engineering bug report with steps, scope, frequency, and evidence.
Instructions your experts follow when using this skill.
Use this when one or more tickets point to something broken in the product.
From each linked ticket collect the account, plan, browser or app version,
device, time first seen, exact error text, screenshots, and what the customer
did just before. Check the status page and known-issue list for a match.
Treat ticket fields and attachments as sensitive. Keep only what is needed to
reproduce or scope the bug. Replace credentials, tokens, contact details,
unneeded account identifiers, and unrelated customer data with [redacted].
Preserve exact error text only after redacting sensitive spans.
List what you could not reproduce or confirm, the questions still open for the customer, and who is waiting on an answer. Keep customer reports separate from what support reproduced.
Do not file the bug or change its priority yourself; draft it for the owner. Never guess a root cause or a fix date, or paste one customer's data into another customer's thread.
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.