[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M797TMADC2B2SNRZ2P524YVC":3,"skill-same:01M797TMADC2B2SNRZ2P524YVC":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M797TMADC2B2SNRZ2P524YVC","scanning-for-data-privacy-issues",null,"Scan for data privacy issues and sensitive information exposure. Use when reviewing data handling practices. Trigger with 'scan privacy issues', 'check sensitive data', or 'validate data protection'.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity--data-privacy-scanner--scanning-for-data-privacy-issues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scanning-for-data-privacy-issues\ndescription: Scan for data privacy issues and sensitive information exposure. Use when reviewing data handling practices. Trigger with 'scan privacy issues', 'check sensitive data', or 'validate data protection'.\nversion: 1.0.0\nallowed-tools: \"Read, Write, Edit, Grep, Glob, Bash(security:*), Bash(scan:*), Bash(audit:*)\"\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [security, scanning-data]\n---\n# Scanning for Data Privacy Issues\n\n## Overview\n\nScan codebases for data privacy violations, PII exposure, and non-compliance\nwith privacy regulations including GDPR, CCPA, HIPAA, and LGPD. This skill\ndetects hardcoded personal data, unprotected PII in logs and databases,\nmissing consent mechanisms, improper data retention, and insufficient\nanonymization or pseudonymization of sensitive fields.\n\n## Prerequisites\n\n- Access to the target codebase and configuration files in `${CLAUDE_SKILL_DIR}\u002F`\n- Knowledge of the data types processed by the application (PII categories, PHI, financial data)\n- Standard shell utilities and Grep\u002FGlob available for pattern matching\n- Reference: `${CLAUDE_SKILL_DIR}\u002Freferences\u002FREADME.md` for scanner API documentation, GDPR compliance guide, and sensitive data pattern definitions\n\n## Instructions\n\n1. Define the PII categories relevant to the application: email addresses, phone numbers, Social Security numbers, credit card numbers, IP addresses, geolocation data, biometric data, health records, and any domain-specific identifiers.\n2. Scan source code for hardcoded PII using regex patterns -- detect email patterns (`[a-zA-Z0-9+_.-]+@[a-zA-Z0-9.-]+`), SSN patterns (`\\d{3}-\\d{2}-\\d{4}`), credit card patterns (Luhn-valid 13-19 digit sequences), and phone number patterns. Flag each as CWE-312 (Cleartext Storage of Sensitive Information).\n3. Examine logging statements (`console.log`, `logger.info`, `logging.debug`, `Log.d`) for PII field references -- flag any logging of user email, password, token, SSN, or credit card fields as CWE-532 (Insertion of Sensitive Information into Log File), severity high.\n4. Analyze database schemas and ORM models for PII fields stored without encryption -- check for columns named `email`, `phone`, `ssn`, `date_of_birth`, `address` that lack encryption-at-rest annotations or transparent data encryption.\n5. Review data transmission: verify PII is transmitted over TLS only, check for PII in URL query parameters (visible in server logs and browser history), and flag unencrypted API responses containing sensitive fields.\n6. Assess consent management: search for cookie consent implementations, privacy policy links, data processing agreements, and opt-in\u002Fopt-out mechanisms. Flag applications collecting PII without documented consent flows as a GDPR Article 6\u002F7 gap.\n7. Check data retention: look for automated data deletion jobs, retention policy configurations, and user data export\u002Fdeletion endpoints (GDPR Article 17 Right to Erasure). Flag absence of retention controls.\n8. Evaluate anonymization and pseudonymization: verify that analytics, reporting, and non-production environments use anonymized or pseudonymized data rather than production PII. Flag test fixtures containing real PII.\n9. Scan configuration files and environment variables for PII used as defaults, seeds, or test data -- flag hardcoded test emails or phone numbers that match real-world patterns.\n10. Classify findings by severity and regulation, produce a data flow diagram identifying where PII enters, is stored, is processed, and exits the system.\n\n## Output\n\n- **PII inventory**: Table of all detected PII types, their locations (file:line), storage mechanism, and encryption status\n- **Findings report**: Each finding includes severity, regulation reference (GDPR Article, CCPA Section, HIPAA Rule), CWE reference (CWE-312, CWE-532, CWE-359), affected file, and remediation steps\n- **Data flow analysis**: Summary of PII entry points (forms, APIs, imports), processing locations, storage mechanisms, and exit points (exports, API responses, logs)\n- **Compliance gap matrix**: GDPR\u002FCCPA\u002FHIPAA requirement mapped to implementation status (Compliant, Gap, Not Applicable)\n- **Remediation plan**: Prioritized actions including field encryption, log sanitization, consent implementation, and retention policy setup\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| High false positive rate on PII patterns | Regex patterns matching non-PII strings (e.g., UUIDs matching SSN patterns) | Refine patterns with context-aware checks; filter results by file type and surrounding code context |\n| Encrypted PII not detected | Application uses transparent encryption that masks PII at the code level | Check encryption configuration separately; mark encrypted fields as \"protected\" in the inventory |\n| Third-party data processors not visible | PII sent to external services via API calls | Grep for HTTP client calls and map destination URLs; flag external services requiring Data Processing Agreements |\n| Large codebase scan timeout | Millions of lines to scan | Scope to high-risk directories first (`src\u002F`, `api\u002F`, `config\u002F`); exclude `node_modules\u002F`, `vendor\u002F`, and build artifacts |\n| Test data flagged as PII exposure | Test fixtures use realistic but fake data | Verify test data is synthetic; recommend using obviously fake data (e.g., `test@example.com`) to avoid false positives |\n\n## Examples\n\n### PII in Application Logs\n\nGrep `${CLAUDE_SKILL_DIR}\u002Fsrc\u002F` for logging statements that reference user fields:\n`logger.info.*email`, `console.log.*password`, `Log.d.*phone`. Flag each match\nas CWE-532, severity high. Recommend implementing a log sanitizer middleware\nthat redacts PII fields before writing to log output.\n\n### GDPR Data Subject Rights\n\nScan `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fapi\u002F` for endpoints supporting data subject rights: user\ndata export (`GET \u002Fapi\u002Fusers\u002F:id\u002Fexport`), data deletion (`DELETE \u002Fapi\u002Fusers\u002F:id`),\nand consent withdrawal. Flag missing endpoints as GDPR Article 15\u002F17\u002F21 gaps,\nseverity high. Recommend implementing a data subject request handler.\n\n### Credit Card Data in Codebase\n\nSearch for credit card number patterns across all source files using\n`\\b[0-9]{13,19}\\b` with Luhn validation context. Check that any payment\nprocessing code uses tokenization rather than storing raw card numbers. Flag\nPAN storage as PCI DSS Requirement 3 violation and CWE-312, severity critical.\n\n## Resources\n\n- [GDPR Full Text](https:\u002F\u002Fgdpr-info.eu\u002F)\n- [CCPA Official Text](https:\u002F\u002Foag.ca.gov\u002Fprivacy\u002Fccpa)\n- [OWASP Top 10 Privacy Risks](https:\u002F\u002Fowasp.org\u002Fwww-project-top-10-privacy-risks\u002F)\n- [CWE-312: Cleartext Storage of Sensitive Information](https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F312.html)\n- [CWE-532: Insertion of Sensitive Information into Log File](https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F532.html)","# Scanning for Data Privacy Issues\n\n## Overview\n\nScan codebases for data privacy violations, PII exposure, and non-compliance\nwith privacy regulations including GDPR, CCPA, HIPAA, and LGPD. This skill\ndetects hardcoded personal data, unprotected PII in logs and databases,\nmissing consent mechanisms, improper data retention, and insufficient\nanonymization or pseudonymization of sensitive fields.\n\n## Prerequisites\n\n- Access to the target codebase and configuration files in `${CLAUDE_SKILL_DIR}\u002F`\n- Knowledge of the data types processed by the application (PII categories, PHI, financial data)\n- Standard shell utilities and Grep\u002FGlob available for pattern matching\n- Reference: `${CLAUDE_SKILL_DIR}\u002Freferences\u002FREADME.md` for scanner API documentation, GDPR compliance guide, and sensitive data pattern definitions\n\n## Instructions\n\n1. Define the PII categories relevant to the application: email addresses, phone numbers, Social Security numbers, credit card numbers, IP addresses, geolocation data, biometric data, health records, and any domain-specific identifiers.\n2. Scan source code for hardcoded PII using regex patterns -- detect email patterns (`[a-zA-Z0-9+_.-]+@[a-zA-Z0-9.-]+`), SSN patterns (`\\d{3}-\\d{2}-\\d{4}`), credit card patterns (Luhn-valid 13-19 digit sequences), and phone number patterns. Flag each as CWE-312 (Cleartext Storage of Sensitive Information).\n3. Examine logging statements (`console.log`, `logger.info`, `logging.debug`, `Log.d`) for PII field references -- flag any logging of user email, password, token, SSN, or credit card fields as CWE-532 (Insertion of Sensitive Information into Log File), severity high.\n4. Analyze database schemas and ORM models for PII fields stored without encryption -- check for columns named `email`, `phone`, `ssn`, `date_of_birth`, `address` that lack encryption-at-rest annotations or transparent data encryption.\n5. Review data transmission: verify PII is transmitted over TLS only, check for PII in URL query parameters (visible in server logs and browser history), and flag unencrypted API responses containing sensitive fields.\n6. Assess consent management: search for cookie consent implementations, privacy policy links, data processing agreements, and opt-in\u002Fopt-out mechanisms. Flag applications collecting PII without documented consent flows as a GDPR Article 6\u002F7 gap.\n7. Check data retention: look for automated data deletion jobs, retention policy configurations, and user data export\u002Fdeletion endpoints (GDPR Article 17 Right to Erasure). Flag absence of retention controls.\n8. Evaluate anonymization and pseudonymization: verify that analytics, reporting, and non-production environments use anonymized or pseudonymized data rather than production PII. Flag test fixtures containing real PII.\n9. Scan configuration files and environment variables for PII used as defaults, seeds, or test data -- flag hardcoded test emails or phone numbers that match real-world patterns.\n10. Classify findings by severity and regulation, produce a data flow diagram identifying where PII enters, is stored, is processed, and exits the system.\n\n## Output\n\n- **PII inventory**: Table of all detected PII types, their locations (file:line), storage mechanism, and encryption status\n- **Findings report**: Each finding includes severity, regulation reference (GDPR Article, CCPA Section, HIPAA Rule), CWE reference (CWE-312, CWE-532, CWE-359), affected file, and remediation steps\n- **Data flow analysis**: Summary of PII entry points (forms, APIs, imports), processing locations, storage mechanisms, and exit points (exports, API responses, logs)\n- **Compliance gap matrix**: GDPR\u002FCCPA\u002FHIPAA requirement mapped to implementation status (Compliant, Gap, Not Applicable)\n- **Remediation plan**: Prioritized actions including field encryption, log sanitization, consent implementation, and retention policy setup\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| High false positive rate on PII patterns | Regex patterns matching non-PII strings (e.g., UUIDs matching SSN patterns) | Refine patterns with context-aware checks; filter results by file type and surrounding code context |\n| Encrypted PII not detected | Application uses transparent encryption that masks PII at the code level | Check encryption configuration separately; mark encrypted fields as \"protected\" in the inventory |\n| Third-party data processors not visible | PII sent to external services via API calls | Grep for HTTP client calls and map destination URLs; flag external services requiring Data Processing Agreements |\n| Large codebase scan timeout | Millions of lines to scan | Scope to high-risk directories first (`src\u002F`, `api\u002F`, `config\u002F`); exclude `node_modules\u002F`, `vendor\u002F`, and build artifacts |\n| Test data flagged as PII exposure | Test fixtures use realistic but fake data | Verify test data is synthetic; recommend using obviously fake data (e.g., `test@example.com`) to avoid false positives |\n\n## Examples\n\n### PII in Application Logs\n\nGrep `${CLAUDE_SKILL_DIR}\u002Fsrc\u002F` for logging statements that reference user fields:\n`logger.info.*email`, `console.log.*password`, `Log.d.*phone`. Flag each match\nas CWE-532, severity high. Recommend implementing a log sanitizer middleware\nthat redacts PII fields before writing to log output.\n\n### GDPR Data Subject Rights\n\nScan `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fapi\u002F` for endpoints supporting data subject rights: user\ndata export (`GET \u002Fapi\u002Fusers\u002F:id\u002Fexport`), data deletion (`DELETE \u002Fapi\u002Fusers\u002F:id`),\nand consent withdrawal. Flag missing endpoints as GDPR Article 15\u002F17\u002F21 gaps,\nseverity high. Recommend implementing a data subject request handler.\n\n### Credit Card Data in Codebase\n\nSearch for credit card number patterns across all source files using\n`\\b[0-9]{13,19}\\b` with Luhn validation context. Check that any payment\nprocessing code uses tokenization rather than storing raw card numbers. Flag\nPAN storage as PCI DSS Requirement 3 violation and CWE-312, severity critical.\n\n## Resources\n\n- [GDPR Full Text](https:\u002F\u002Fgdpr-info.eu\u002F)\n- [CCPA Official Text](https:\u002F\u002Foag.ca.gov\u002Fprivacy\u002Fccpa)\n- [OWASP Top 10 Privacy Risks](https:\u002F\u002Fowasp.org\u002Fwww-project-top-10-privacy-risks\u002F)\n- [CWE-312: Cleartext Storage of Sensitive Information](https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F312.html)\n- [CWE-532: Insertion of Sensitive Information into Log File](https:\u002F\u002Fcwe.mitre.org\u002Fdata\u002Fdefinitions\u002F532.html)",{"name":5,"tags":24,"author":27,"license":15,"version":28,"description":7,"allowed-tools":29,"compatible-with":30},[25,26],"security","scanning-data","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Read, Write, Edit, Grep, Glob, Bash(security:*), Bash(scan:*), Bash(audit:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsecurity--data-privacy-scanner--scanning-for-data-privacy-issues",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill scanning-for-data-privacy-issues",{"tool":46,"command":47},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill scanning-for-data-privacy-issues",{"tool":49,"command":50},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill scanning-for-data-privacy-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity--data-privacy-scanner--scanning-for-data-privacy-issues\u002FSKILL.md",true,[],[55,62,69,76,83,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]