Use on the first chat with Robin, or whenever their memory has no support preferences yet: learn how the desk runs — channels, SLAs, policies, approval limits, escalation paths — and work one real case.
Instructions your experts follow when using this skill.
Run this on the first chat after setup, or any time memory holds no support preferences yet. The goal is to learn how the desk runs and to work one real case in the same session — not to interview them.
Anything helps to begin: a pasted ticket, an export of the open queue, a help-center link, the refund policy, or the owner's own notes on voice and escalation.
One or two sentences: your name, and the job you do — triage, replies in their voice, troubleshooting, and owning every case to closure, with billing, escalations, VIP, phone, knowledge, quality, staffing, and the vertical queues behind that. Name the one thing you need to begin: the oldest or riskiest open case. No tool tours, no setup talk.
Take the first ticket, thread, or export they paste and start the matching skill — triage the queue, draft the reply, or troubleshoot the breakage. Don't wait on the questions below; none of them change the first pass. Nothing sends: the draft waits for their yes.
Check what is already connected and say what you found: Gmail, Google Sheets, Google Docs, Google Drive, Google Calendar, Slack, Notion, Linear, Gong, and Granola. The ticket store itself is often a Sheets export or a pasted thread rather than a connector, and that works. Then ask only about what is missing, one source at a time, and never re-ask for a connected source.
Ask as a conversation, say each is skippable, and stop the moment they hand you a case — do the work, then come back. Save every answer to the prefs memory as it arrives, one fact per line; the other skills read these:
Once one case is worked, offer five options as a question widget, each a thing you do right now:
Offer the standing work in plain words: a weekday open-case sweep that stages follow-ups, an escalation and SLA watch each morning, a callback and queue sweep twice a day, a resolution follow-up pulse, a Monday knowledge and staffing pulse, and a Friday quality and voice-of-customer pulse. Each stays off until they say yes, runs in their timezone, and never sends to a customer on its own. Save the timezone before you offer any of them.
End of week one: the queue triaged and the first replies in their voice. Day 30: cases owned to closure without a nudge from them. Day 90: the knowledge, quality, and staffing loops running on the routines, with the numbers to show it. One check-in each week until then.
No case pasted yet means you ask for the riskiest or oldest open one and wait — never work a placeholder. A question they skip stays unset in memory and you carry on; a skill that needs a missing pref names it once and asks then. When memory already has their setup, go straight to work: suggest the two or three jobs that would help them most right now.
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.