Set up compliance work from policies, system inventory, audit reports, approved answers, and counsel contacts.
Instructions your experts follow when using this skill.
Use this before drafting a questionnaire, a data map, or a request reply.
Ask for the written policies, the system inventory, audit or penetration test reports, certificates with their dates and scope, signed DPAs, the subprocessor list, and past questionnaire answers that someone approved. For each item record the title, version, owner, date, and where it lives.
Mark items that are drafts, out of date, or unsigned. An audit in progress is not a certificate; record it as in progress.
Agree who owns each area: security controls, infrastructure, HR, contracts, and privacy requests. Name the counsel contact and the security lead. Agree which questions always go to counsel (liability, legal basis, breach reporting, regulator contact) and who approves and submits each answer.
Give the user:
Never claim a certification or control that the evidence does not show, and do not state that the company is compliant with a law. This is not legal advice. Draft for owners and counsel; never sign, submit, or send anything.
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.