pii-guard

Scan outbound content for personally identifiable information and block git pushes.

23|5|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/EverClaw/EverClaw --skill pii-guard-everclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pii-guard
Source: https://github.com/EverClaw/EverClaw/tree/main/skills/pii-guard
Command: npx skills add https://github.com/EverClaw/EverClaw --skill pii-guard-everclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental disclosure of personally identifiable information before content is sent outside the workspace, helping you avoid privacy breaches and compliance incidents.

Core Features & Use Cases

  • Outbound Content Scanning: Checks text, files, and repository content for protected names, emails, phone numbers, wallet addresses, locations, and other sensitive strings.
  • Pre-Push Enforcement: Blocks git pushes when sensitive data appears in staged or outgoing changes, with support for global hook installation.
  • Audit and Setup Workflow: Installs a reusable scanner, manages protected pattern files, and supports history scanning to catch past exposures.
  • Use Case: Before publishing a draft, sending a message, or pushing code, the Skill verifies that no protected personal data is about to leave your system.

Quick Start

Ask the skill to scan the target file, message, or repository for personal data before you send or publish it externally.

Frequently Asked Questions about pii-guard

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

FAQPage Schema
How do I prevent sensitive personal data from leaking in a git push?

Scanning content for personally identifiable information before external transmission identifies protected names, emails, phone numbers, and wallet addresses. It prevents privacy breaches by verifying that no sensitive data leaves your system during publishing or messaging.

How do I scan my repository history for past exposures of personally identifiable information?

To scan repository history for past exposures of personally identifiable information, you can run a history scanning workflow. This checks previous commits for protected strings to catch and audit sensitive data that may have already been transmitted.

Does git pre-push hook scanning work for outbound emails and attachments too?

Git pre-push hook scanning focuses on repository content, but the broader scanning mechanism extends to outbound emails, attachments, and social publishing. It checks text and files for sensitive strings before any external transmission occurs.

Do I need jq and git installed to set up automated PII content scanning?

Yes, jq and git are required dependencies to set up automated PII content scanning. These tools support global hook installation, pattern file parsing, and the reusable scanner needed to enforce hard-blocks on sensitive data transmission.

What happens when the pre-push hook detects protected patterns in my staged changes?

When the pre-push hook detects protected patterns in your staged changes, it applies hard-block enforcement to stop the push. It generates override-aware review output so you can evaluate flagged sensitive data before any external transmission.

Can I configure custom pattern scanning for specific wallet addresses and locations?

Yes, you can configure custom pattern scanning for specific wallet addresses and locations. The audit workflow manages protected pattern files, allowing you to define and scan for sensitive strings tailored to your data protection requirements.