Use before card, personal, or health data moves: redact PCI, handle PII and PHI by the regime, and contain spills fast.
Instructions your experts follow when using this skill.
Use this before card, personal, or health data moves: redact PCI card data, handle PII and PHI (protected health information) by the regime, and contain spills fast.
You need the draft, transcript, or record to check, the regimes and redaction tool from prefs, and the vault or safe-store path.
Call out card numbers and CVVs, government IDs, passwords and tokens, health details, and any other identifiers. Give each finding its data type and line number with a redacted fragment only — never reproduce the raw value, not in the finding, the log, or anything you hand back, because the masking step comes later and a quoted PAN, CVV, token or health detail has already escaped by then. A scan you cannot run is UNKNOWN, never "clean".
Mask card data to last four, strip CVVs and full credentials entirely, and minimize PII to what the case needs. Fix what a reword can fix and mark each change; route what it cannot — data already exposed, a required record that must keep identifiers — to the compliance owner with a short packet.
On payment calls, pause recording or mask keypad (DTMF) entry before collection, and resume after authorization. Never store sensitive authentication data — CVV, PIN, or magnetic-stripe track data — in audio, screen recordings, or transcripts; the recording itself becomes the violation. Redact any such slip from transcripts immediately.
Confirm minimum-necessary access (except treatment, disclosures to the individual, authorized uses, disclosures to the regulator, or as required by law), identity verified before any PHI talk, encrypted store, no health detail in ticket subjects or public replies, and and retention on the applicable PHI schedule — keep the record only as long as it is genuinely needed, and scope the six-year default to the compliance documentation that actually requires it rather than to every case record. A PHI finding outside the safe path is P1 until contained.
Stamp the result: clean, redacted, or blocked-with-owner. Blocked items never move before the compliance yes. Log regimes, verdict, and approver on the case.
After a spill, draft the containment note: what leaked, where, who saw it, the purge or rotate steps, and the prevention fix. Offer to re-check the macro or template source so the next use starts clean.
Deliver the findings list, the redacted text or the owner packet, the verdict stamp, and the case log line.
No redaction tool means manual masking with a second pair of eyes required, and the tool gap named. Never declare text clean by skimming.
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.