Prepare a data subject request reply with identity check, scope, deadline, and systems to search.
Instructions your experts follow when using this skill.
Use this for an access, deletion, correction, or objection request.
Record the date received, the channel, the requester, and exactly what they asked for, quoted. Note the deadline from the company's own procedure and the date it falls on. Check identity with the method the procedure names; if the check has not passed or cannot be read, stop and say so.
List the systems from the data map that may hold this person's data, with the owner of each. For each system note:
Draft a short, plain reply that confirms the request, says what happens next, and gives the date the requester can expect an answer. For deletion, list the systems in scope and any records the procedure says must be kept, with the source of that rule. Put anything that needs a legal view in a note for counsel.
Never delete, export, or change data yourself, and do not send the reply or claim a search is complete without each owner's confirmation. This is not legal advice.
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.