← ClaudeAtlas

pii-scanlisted

Find personal data leaking into analytics URLs, page paths and event parameters. Use when auditing GA4, Google Tag Manager, server logs or any tracking export for emails, phone numbers, card numbers, IBANs, tokens or names that should never have reached an analytics platform. Runs on a CSV or log file you already have, needs no API access, and never prints an unredacted value.
m7mdwb/martech-verify · ★ 4 · Data & Documents · score 75
Install: claude install-skill m7mdwb/martech-verify
# pii-scan ## Agent workflow This is an executable audit, not a checklist. When a usable file is available, run the bundled scanner instead of only explaining how someone could scan it. 1. Identify the export the user wants checked. If several files are plausible and the choice changes the audit, ask which one; otherwise use the clearly relevant file. 2. Resolve `scripts/scan.py` relative to this `SKILL.md` and run it with an available Python 3 interpreter. In Claude Code, `${CLAUDE_SKILL_DIR}` is this skill directory; in other hosts use the skill path supplied by the host. Quote every path. 3. Let column auto-detection run first. Add `--column NAME` only when the user named a column or the report shows that the wrong one was selected. Use `--json` only when the user wants machine-readable output. 4. Interpret exit codes exactly: `0` means the supplied export produced no findings, `1` means findings were produced, and `2` means the input could not support a trustworthy scan. On `2`, relay the actionable error and ask for the smallest correction; never describe the file as clean. 5. Summarize the highest-severity verified findings first, preserve the distinction between `!` verified values and `?` name-only signals, and give the first remediation step. Do not reveal, reconstruct, or repeat an unredacted personal value. Never modify the source export, upload it, or invent findings beyond the scanner's output. If the user needs help preparing an