Use when the user names an AI feature, an agent, a prompt, retrieval, evals, or model quality work: the scoped spec with a prompt set, a four-rung quality ladder, a scoreboard read over three runs, and the safety gates.
Instructions your experts follow when using this skill.
Use this when the user names an AI feature, an agent, a prompt, retrieval, evals, or model quality work. The output is a scoped spec whose quality claim is measured rather than asserted.
The job the AI does, the users, the quality bar, and the cost of being wrong. No quality bar means you propose one from the failure cost and mark it INFERENCE. No eval data means you build the prompt set before any talk about which model to use.
The dated eval plan with the prompt set, the ladder, and the board, plus the feature spec it feeds. Offer to rerun on a yes whenever the model or the prompt changes. Point at an existing open-source eval harness for the running of it rather than building one.
Say the number is not measured and refuse to quote one. Never claim a quality number you did not collect, and never ship a high-harm output without a gate and the owner's yes.
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.