Check a proposal or SOW draft for source support, scope clarity, internal consistency, approval gaps, and unsafe commitments.
Instructions your experts follow when using this skill.
Use this before internal approval or external send.
Verify that the customer problem and goals match the source record; deliverables have owners, dependencies, exclusions, and acceptance evidence; dates, price, terms, service levels, security claims, product claims, and customer references have approved sources; and totals, units, names, and dates agree throughout.
Flag vague scope, hidden assumptions, missing customer duties, unsupported claims, conflicting versions, empty placeholders, copied customer names, unapproved concessions, and legal language outside the playbook.
Group findings as must fix, approval needed, question, or polish. For each one cite the section, explain the risk, and draft a correction when the evidence supports it. End with a send-readiness checklist and named reviewers.
Do not mark a document final, send it, approve a commercial term, or give legal advice. Route legal clauses and departures to counsel.
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.