
Pii Detect
- 674 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
pii-detect is a security scanning skill that flags personally identifiable information and secrets in text, code, and configs for developers who must prevent PII from entering commits, logs, or model responses.
About
pii-detect is a PII and secrets detection skill from ruvnet/ruflo that scans text, code, and configuration before data enters commits, logs, storage, or LLM responses. It targets emails, phone numbers, SSNs, API keys, passwords, and related sensitive patterns through aidefence MCP tools including aidefence_has_pii, aidefence_scan, aidefence_analyze, and transfer_detect-pii, with Bash available for local inspection. Developers invoke pii-detect with an input-text argument hint when reviewing diffs, sanitizing logs, or validating agent output prior to push. The skill complements broader security review by catching accidental credential and identity leakage early in the development loop rather than after production exposure.
- pii-detect
Pii Detect by the numbers
- 674 all-time installs (skills.sh)
- +7 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #541 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill pii-detectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 674 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you detect PII in code before committing?
Use pii-detect for development tasks
Who is it for?
Developers and agent builders who must scrub commits, logs, and LLM responses for PII and credentials before storage or release.
Skip if: Teams seeking full application security audits or compliance certification workflows that extend beyond automated PII and secret pattern detection.
When should I use this skill?
User is about to commit code, write logs, store data, or send model responses that may contain emails, credentials, or other PII.
What you get
PII and secret detection report listing flagged emails, phone numbers, SSNs, API keys, and passwords in scanned input.
- PII detection report
- flagged secret locations
Files
PII Detection
Detect personally identifiable information before it enters logs, commits, or responses.
When to use
Before committing code, storing data, or sending responses that might contain PII (emails, phone numbers, SSNs, API keys, passwords).
Steps
1. Quick PII check — call mcp__claude-flow__aidefence_has_pii with the text for a boolean result 2. Detailed scan — call mcp__claude-flow__transfer_detect-pii for categorized PII findings 3. Full analysis — call mcp__claude-flow__aidefence_analyze for context-aware PII detection 4. If PII found, flag the specific locations and suggest redaction
PII categories detected
- Email addresses, phone numbers
- Social security numbers, tax IDs
- Credit card numbers
- API keys, tokens, passwords
- Physical addresses
- Names linked to sensitive data
Related skills
FAQ
What PII types does pii-detect flag?
pii-detect flags emails, phone numbers, SSNs, API keys, passwords, and related sensitive patterns in text, code, and configurations. Developers run it before commits, logging, storage, or sending model responses that might leak identity data.
Which tools does pii-detect use to scan?
pii-detect calls aidefence MCP tools including aidefence_has_pii, aidefence_scan, aidefence_analyze, and transfer_detect-pii, with Bash permitted for local file inspection during agent-driven scans.