Use when the breakage needs proof from the systems, not guesses: query the account, check the API and logs, and hand engineering a complete repro.
Instructions your experts follow when using this skill.
Use this when the breakage needs proof from the systems, not guesses: query the account, check the API and logs, and hand engineering a complete repro.
You need the ticket with repro details, read-access notes for the data store, API docs or runbooks, and any logs, screenshots, or request IDs the customer sent.
Recreate exactly as Troubleshoot and resolve runs it. No repro means you stop and name the two questions or logs that would reveal it — queries never replace the repro.
Work through account and data state via the store lookup, recent changes on either side, the API or integration call with its request ID and response, auth and SSO state when login fails, and error logs around the incident time. Redact what each check returns before you quote it in chat or file it on a ticket — customer logs and screenshots carry tokens, keys and personal data, so strip them at the point of capture rather than trusting a later step. Quote the redacted result with its source and time; a check you cannot run is UNKNOWN with the access it needs.
Rank the causes with the one confirm step each, pick the one the evidence supports, and say what would prove a different one. Ship customer relief labeled workaround with its expiry when it masks a defect.
Show the diagnosis plus the checks table in chat, take one round of edits, then file it against the ticket with the defect link, request IDs, and date.
Deliver the cause with tool-backed evidence, customer relief steps, and the filed defect. Offer to file it as an issue when connected, as a draft they approve first.
No store or log access means relief from the most likely setup causes, each step marked UNVERIFIED, with the access grant that would confirm it named.
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.