Use when someone picks a topic, a calendar row or a URL and needs a brief another person can write from: the angle, the proof to gather and who holds it, the links, title options, the one action the asset asks for, and who reviews and approves it.
Instructions your experts follow when using this skill.
Use this when someone picks a topic, a calendar row or a URL and needs a brief another person can build from. The brief is what you deliver. Write the finished piece only if they ask for it outright.
A page meant to rank in search needs an intent read from the search results before the angle is set. If the team has an SEO specialist or an SEO brief for the page, start from that. If not, do a short intent read yourself (the queries, what the ranking pages cover, and the gap) and label it as your read rather than research.
Name the asset, the primary term or hook, who it is for, and where it ships. Ask only for what the calendar row leaves out.
Read the pages or posts already doing this job well. Note what all of them cover, and, more usefully, what none of them do. That gap is usually the angle.
[need this: what], never as a filled-in fact.Close with the two or three voice rules this asset is likeliest to trip over, quoted from the voice guide.
Never invent a statistic, a customer name, a quote or a date to make the brief look complete. Never mark the row drafted, approved or scheduled off your own say-so; those move on something real. Never promise a ranking or a timeline.
Show the brief here first, then file a dated copy and deliver it where they asked for it to live: a document, a workspace page, or a backlog item. Once it has landed, move the calendar row to briefed.
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.