wrdn-pii

Detect real personal identifiers and customer data in code changes and artifacts.

Updated Aug 3, 2025
One-click install
npx skills add https://github.com/cschmatzler/nixos-config --skill wrdn-pii-cschmatzler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-pii
Source: https://github.com/cschmatzler/nixos-config/tree/main/modules/_pi/skills/warden-skills/wrdn-pii
Command: npx skills add https://github.com/cschmatzler/nixos-config --skill wrdn-pii-cschmatzler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers distinguish real personally identifiable information and customer-specific data from synthetic or example data that often appears in code, tests, docs, and fixtures, preventing false alarms and privacy breaches.

Core Features & Use Cases

  • Identify real emails, customer org slugs, revenue-related figures, and other customer-confidential identifiers in code, tests, fixtures, logs, and payloads.
  • Validate context with a trace-first approach by considering surrounding lines, file path, and sink exposure (logs, URLs, or exports) before reporting.
  • Provide actionable remediation guidance, including data redaction, hashing, or replacing with synthetic placeholders, and suggest targeted scopes for auditing.

Quick Start

Review a diff and identify any real PII or customer-confidential data, then output structured findings with remediation guidance.

Frequently Asked Questions about wrdn-pii

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect real PII and customer data in code diffs and test fixtures?

Detect real PII and customer data in code by analyzing diffs, tests, and fixtures to separate authentic customer information from synthetic example data, returning structured findings with file, line, sink, and remediation guidance.

What is the best way to identify actual customer identifiers in logs and API responses?

Identify customer identifiers in logs and API responses by tracing data flow to appropriate sinks like URLs and exports, validating context using surrounding lines and file paths before reporting real personal data exposure.

How does PII detection distinguish between fake example data and authentic customer information?

PII detection distinguishes fake from authentic data by applying a trace-first approach that evaluates surrounding lines, file paths, and sink exposure to prevent false alarms while accurately flagging real customer-confidential identifiers.

Can I scan configuration files and telemetry payloads for personal identifiers without false positives?

Scan configuration files and telemetry payloads for personal identifiers with reduced false positives by validating context against file paths, surrounding code, and sink exposure before flagging authentic customer-specific data.

What remediation steps are suggested when real personal data is found in code artifacts?

Remediation for real personal data in code artifacts includes data redaction, hashing, or replacing with synthetic placeholders, along with targeted scopes for auditing to prevent further privacy breaches.

Does PII redaction in code changes require parsing specific file formats or dependencies?

PII redaction in code changes requires no external dependencies, applying directly across diffs, docs, configs, logs, telemetry, and API responses to trace data flow and output structured severity findings.