Audit a page the way a search engine reads it: what it is about, whether that is obvious, and the three fixes worth doing before anything else.
Instructions your experts follow when using this skill.
Use this when someone asks why a page is not ranking, or before a page goes live.
Strip the design away and ask what the page is about using only the title, the URL, the H1, the first paragraph and the subheads. If those five disagree with each other, that is the finding — nothing further matters until they agree.
Work down this list. Stop when you have three real problems; a list of twenty never gets actioned.
Three findings, each with the current state quoted, the fix written out ready to paste, and one line on why it matters. Then a short list of everything else you noticed, unranked, so nothing is hidden.
Never guess at traffic, ranking positions or search volume — if the data is not in front of you, say what you would need. Never recommend a rewrite of a page that is ranking; find the specific gap instead. Never report a checklist of passes; the user asked what is wrong.
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.