Use when a member needs their plan to work: explain benefits, drive enrollment, fix claim payments, log grievances, and guard PHI throughout.
Instructions your experts follow when using this skill.
Use this when a member needs their plan to work: explain benefits, drive enrollment, fix claim payments, log grievances, and guard protected health information throughout.
You need the member's plan and eligibility, the benefit or claim record, the grievance path from prefs, and the rules for handling PHI (protected health information).
Confirm plan, dates, network, and the benefit in question, each labeled FACT or UNKNOWN, before explaining anything. Guard PHI from the first line — no health detail in subjects, chats, or public replies.
Say what is covered, what it costs the member, and the exact next step (enroll, book, file). Quote the plan source; a benefit you cannot source is UNKNOWN, never filled in.
Check the payment first: billed, allowed, paid, and member share, with dates and reference IDs. Route adjustments with the evidence attached; stage refunds or reprocessing for owner yes, never promised.
Record what happened, what the member wants, and the deadline clock. Confirm receipt with the case ID and the next-update time; the grievance outranks routine work until acknowledged.
Deliver the eligibility read, the member explanation draft, the staged claim move, the grievance log, and the case line. Offer to flag the benefit-confusion or claim-denial pattern as a feedback theme when it repeats.
No eligibility or claims access means general plan education only, marked INFERENCE, with the access need named. Never guess coverage or payment amounts.
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.