gdpr-auditor
Comprehensive GDPR compliance auditing plugin that analyzes static code files, database schemas, and configurations for EU data protection regulation compliance. Includes 8 reference documents, 5 automated scanning tools, and generates detailed compliance audit reports.
Overview
Professional Security, Compliance, and Productivity Plugins for Claude Code
    
A curated collection of production-ready security, compliance, and productivity plugins for Claude Code. Built on authoritative sources and rigorously tested with real-world data.
π Documentation Wiki
[β Full Documentation Wiki (53 pages)](https://github.com/diegocconsolini/ClaudeSkillCollection/wiki)
| Category | Topics |
|---|---|
| Getting Started | Installation, First Session, Quick Reference |
| Configuration | CLAUDE.md, Memory Architecture, Settings, Permissions |
| MCP Servers | Transports, Scopes, Authentication, Troubleshooting |
| Plugins | Lifecycle, Plugins vs MCP, Creating Plugins |
| Context | What Consumes Context, Reduction Strategies, Subagent Delegation |
| Sessions | Task-Based Config, When to Restart, Workflow Patterns |
| Platforms | macOS, Linux, WSL2, Windows Native |
| Examples | 14 copy-paste examples for CLAUDE.md, MCP, Workflows, Settings |
π Quick Start
Step 1: Add Marketplace (GitHub Repository)
# IMPORTANT: Use GitHub repository format for remote updates
/plugin marketplace add diegocconsolini/ClaudeSkillCollectionβ οΈ Critical: Do NOT use local paths like /path/to/ClaudeSkillCollection as this prevents remote updates. Always use the GitHub format owner/repo for automatic updates.
Step 2: Install Plugins
# Install desired plugins from the marketplace
/plugin install plugin-security-checker@security-compliance-marketplace
/plugin install gdpr-auditor@security-compliance-marketplace
/plugin install pdf-smart-extractor@security-compliance-marketplaceStep 3: Enable Plugins and Restart
After installation:
- Enable plugins via
/plugininterface (plugins are disabled by default after first install) - Restart Claude Code to load the plugins properly
Updating Plugins
# To get updates from GitHub:
/plugin # Navigate to plugin details and select "Update now"
# If you installed with a local path and can't update:
/plugin marketplace remove security-compliance-marketplace
/plugin marketplace add diegocconsolini/ClaudeSkillCollection # Re-add using GitHub formatπ Plugin Categories
π Security & Compliance (Authoritative Sources)
Professional security and compliance plugins built from official regulatory texts, industry frameworks, and authoritative guidance. No hallucinated content - every template, requirement, and guideline is traceable to its source.
What makes these authoritative:
- β’GDPR Auditor: EUR-Lex official EU regulation texts, ICO guidance, EDPB guidelines
- β’Cybersecurity Policy Generator: SANS Institute templates, CIS Controls v8 official framework
- β’Incident Response Playbook Creator: NIST SP 800-61r3 (April 2025), CISA federal playbooks, GDPR Article 33/34, HIPAA Breach Notification Rule
π Productivity Tools (Smart Extraction with Persistent Caching)
High-performance document extraction plugins that solve the "PDF/Excel/Word too large for LLM" problem through local extraction, semantic chunking, and intelligent caching.
How caching works (v2.0.0 - Unified System):
- First extraction: Processes document locally (PyMuPDF for PDF, openpyxl for Excel, python-docx for Word)
- Persistent cache: Stores extracted content in
~/.claude-cache/{doc_type}/with SHAKE256 hash keys (SHA-3 family) - Subsequent queries: Instant - uses cached extraction, no re-processing needed
- Token optimization: 10-100x reduction by loading only relevant chunks, not entire documents
- Automatic migration: Old caches (SHA-256) automatically migrate to new format (SHAKE256)
All three extractors share unified caching: Local extraction β Semantic chunking β Persistent caching β Efficient querying
What's new in v2.0.0:
- β’Unified cache location:
~/.claude-cache/(was~/.claude-{type}-cache/) - β’Modern hashing: SHAKE256 (was SHA-256)
- β’Automatic migration from v1.x caches
- β’Shared caching library for consistency
- β’See
/shared/CACHE_STRATEGY.mdfor details
β οΈ IMPORTANT: Cache Location Behavior
Extracted files are stored in user cache directory, NOT your working directory:
Cache locations by platform:
- β’Linux/Mac:
~/.claude-cache/{pdf,xlsx,docx}/{document_name}_{hash}/ - β’Windows:
C:\Users\{username}\.claude-cache\{pdf,xlsx,docx}\{document_name}_{hash}\
Why cache directory instead of working directory?
- β’Cross-project reuse: Same document analyzed from different projects uses the same cache
- β’Persistent caching: Extract once, query forever (even after closing Claude Code)
- β’Performance: Subsequent queries are instant (no re-extraction)
- β’Disk space efficiency: One extraction shared across all projects
Accessing cached content:
# List all cached documents
python scripts/query_{pdf,xlsx,docx}.py list
# Query specific document
python scripts/query_pdf.py search {cache_key} "your search"
# Copy cache to working directory (if needed)
cp -r ~/.claude-cache/pdf/{cache_key}/* ./extracted/Note: Cache is local and not meant for version control. Keep original documents in your repo and let each developer extract locally (one-time operation).
π Security & Compliance Plugins
1. Plugin Security Checker
Production Ready β’ v3.0.0 β’ Plugin Vulnerability Scanner
Advanced security scanner for Claude Code plugins with 91 specialized pattern detection agents. Performs static code analysis to detect vulnerabilities, code obfuscation, hardcoded credentials, and security anti-patterns before you install untrusted plugins.
Technical Foundation:
- β’IntelligentOrchestrator: Consensus voting across 91 specialized agents
- β’AccuracyCache: Bloom filter + Trie hybrid with zero false positives
- β’MITRE ATT&CK/ATLAS: Framework mapping for attack technique identification
- β’Adaptive Learning: Auto-evolving rules from validated detections
- β’Real-World Testing: Successfully scanned 987 plugins from 15 marketplaces (100% scan success rate)
Key Features:
- β’91 Specialized Agents - 17 CRITICAL, 39 HIGH, 23 MEDIUM, 2 LOW severity patterns
- β’Consensus Voting - Multiple agents vote on each detection with conflict resolution
- β’Dangerous Function Detection - Python (eval, exec, os.system) and JavaScript (eval, innerHTML)
- β’Code Obfuscation Detection - Base64 encoding, hex encoding, character obfuscation
- β’Credential Scanning - Hardcoded API keys, passwords, cloud credentials, private keys
- β’Schema Validation - Validates plugin.json structure and configurations
- β’CVE Mapping - Links findings to CVE-2025-52882, CVE-2025-54794, CVE-2025-54795, CVE-2025-59828
- β’OWASP API Top 10 - Mappings to API1 (BOLA), API2 (Auth), API7 (SSRF), API8 (Misconfig)
- β’Comprehensive Reporting - JSON, Markdown, and HTML report generation
Real-World Results:
- β’Scanned 987 plugins across 15 marketplace repositories
- β’CRITICAL Risk: 3 plugins (0.3%)
- β’HIGH Risk: 1 plugin (0.1%)
- β’LOW Risk: 982 plugins (99.5%)
- β’Test Results: 29/29 tests passed (100%)
- β’Memory Usage: ~17 MB (3.4% of 500MB budget)
- β’Cache Throughput: 11,111 ops/sec
Use Cases:
- β’Pre-installation security scanning of Claude Code plugins
- β’Vulnerability assessment of plugin code before running
- β’Security auditing of plugin repositories and marketplaces
- β’Identifying malicious or suspicious code patterns
- β’Validating plugin compliance with security best practices
- β’Research and analysis of plugin security landscape
Who Should Use:
- β’Anyone installing Claude Code plugins from third-party sources
- β’Plugin developers testing their own plugins for security issues
- β’Security researchers analyzing the plugin ecosystem
- β’Organizations with strict security policies for tooling
- β’Marketplace maintainers validating submitted plugins
- β’Security teams conducting defensive security assessments
Commands:
# Scan a single plugin
python3 scripts/scan_plugin.py /path/to/plugin
# Scan with JSON output
python3 scripts/scan_plugin.py /path/to/plugin --output scan.json --format json
# Generate Markdown report
python3 scripts/generate_report.py scan.json --format markdown --output report.md
# Using IntelligentOrchestrator (Python API)
from intelligent_orchestrator import IntelligentOrchestrator
orchestrator = IntelligentOrchestrator(
patterns_file="references/dangerous_functions_expanded.json",
max_memory_mb=500
)
detections = orchestrator.scan_file("plugin.py", code)
orchestrator.export_findings("findings.json")Important Disclaimer: This is a SUPPORTING TOOL for preliminary security checks only. It does NOT guarantee plugin safety. Always review source code manually before installing plugins. You are ultimately responsible for plugins you install.
β View Plugin Security Checker Documentation
2. GDPR Auditor
Production Ready β’ v1.0.0 β’ Data Privacy & Compliance
Comprehensive GDPR compliance auditing plugin that analyzes static code files, database schemas, and configurations for EU data protection regulation compliance.
Authoritative Sources:
- β’EUR-Lex: Official GDPR regulation text (EU 2016/679)
- β’ICO (UK Information Commissioner's Office): Implementation guidance
- β’EDPB (European Data Protection Board): Official interpretations and guidelines
- β’8 reference documents totaling 2.1MB of official compliance materials
Key Features:
- β’Scans source code for personal data collection patterns
- β’Analyzes database schema files (SQL DDL, migrations) for sensitive data
- β’Verifies data subject rights implementation (access, rectification, erasure)
- β’Audits security measures and encryption configurations
- β’Generates detailed compliance audit reports with specific article references
- β’5 automated scanning tools (static file analysis only - no live system access)
Use Cases:
- β’Pre-launch GDPR compliance checks for EU market entry
- β’Regular compliance audits and monitoring
- β’Privacy policy development and validation
- β’Data protection impact assessments (DPIA)
- β’Third-party vendor security assessments
- β’Audit preparation (ISO 27001, SOC 2, GDPR)
Who Should Use:
- β’Web application developers handling EU user data
- β’DevOps and infrastructure teams
- β’Privacy officers and DPOs (Data Protection Officers)
- β’Security consultants and auditors
- β’Startup founders preparing for EU markets
- β’Legal and compliance teams
β View GDPR Auditor Documentation
3. Cybersecurity Policy Generator
Production Ready β’ v1.0.0 β’ Security Governance & Compliance
Professional cybersecurity policy document generator using 51 industry-standard templates from SANS Institute and CIS Controls. Creates complete, framework-compliant policy documents customized for your organization.
Authoritative Sources:
- β’SANS Institute: 36 policy templates from the industry-leading security training organization
- β’CIS Controls v8: 15 additional templates from the Center for Internet Security
- β’ISO 27001: Compliance mappings to information security management standard
- β’NIST CSF: Cybersecurity Framework function and category mappings
- β’SOC 2: Trust Service Criteria alignment (Security, Availability, Confidentiality)
- β’320KB of reference data with verified compliance framework mappings
Key Features:
- β’51 professional policy templates (36 SANS + 15 CIS Controls)
- β’Interactive AskUserQuestion workflow with Claude Code's native UI
- β’Multi-framework compliance mappings (ISO 27001, SOC 2, NIST CSF, CIS Controls v8, GDPR)
- β’Multi-format generation (Markdown, Word, HTML, PDF)
- β’15 security policy categories covering all InfoSec domains
- β’Organization customization with branding options
- β’4 automated policy generation scripts
Policy Categories:
- β’Governance (13 policies) - Information Security, Acceptable Use, Password Management
- β’Identity & Access (8 policies) - Access Control, Authentication, Remote Access
- β’Application Security (7 policies) - Secure Development, API Security, Code Review
- β’Compute & Network (10 policies) - Cloud Security, Network Security, Virtualization
- β’Data Protection (2 policies) - Data Classification, Data Recovery & Backup
- β’Operations, Resilience, Risk (11 policies) - Incident Response, Change Management, Risk Assessment
Real-World Testing:
- β’Production deployment: Guatemaltek (October 2025)
- β’Generated: 8 foundational security policies
- β’Formats: Markdown + Word (.docx)
- β’Result: Production-ready policies deployed to internal security program
Use Cases:
- β’Starting a new security program (foundational policies)
- β’Preparing for compliance audits (ISO 27001, SOC 2, NIST CSF)
- β’Updating outdated or missing security policies
- β’Meeting cyber insurance or vendor security requirements
- β’Building comprehensive policy documentation for framework compliance
Who Should Use:
- β’CISOs and security leaders starting or improving security programs
- β’Compliance officers preparing for audits
- β’Startups establishing security governance
- β’IT managers needing standardized policies
- β’Consultants creating client security documentation
- β’Organizations pursuing ISO 27001, SOC 2, or NIST compliance
β View Cybersecurity Policy Generator Documentation
4. Incident Response Playbook Creator
Production Ready β’ v2.0.0 β’ Incident Response & Security Operations
Professional incident response playbook generator based on NIST SP 800-61r3 and authoritative sources. Creates comprehensive, customized IR documentation covering modern threat landscape with built-in GDPR and HIPAA compliance guidance.
Authoritative Sources:
- β’NIST SP 800-61r3: Computer Security Incident Handling Guide (April 2025 revision)
- β’NIST SP 800-218: Secure Software Development Framework (SSDF)
- β’NIST SP 800-161r1-upd1: Cybersecurity Supply Chain Risk Management (C-SCRM)
- β’NIST SP 800-190: Application Container Security Guide
- β’NIST SP 800-82r3: Guide to Operational Technology (OT) Security - ICS
- β’NIST IR 8228: IoT Device Cybersecurity Capability Core Baseline
- β’AWS Security Incident Response Guide
- β’CISA DDoS Attack Response Guide
- β’OWASP API Security Top 10 2023
- β’NIST Cybersecurity Framework 2.0: Function and category mappings (February 2024)
- β’GDPR (EU 2016/679): Article 33 (72-hour breach notification) and Article 34 (data subject notification)
- β’HIPAA Breach Notification Rule: 45 CFR Β§Β§164.400-414 (60-day timeline)
- β’288KB total reference data (incident_scenarios_v2.json: 58KB, 11 scenarios)
Key Features:
- β’11 comprehensive incident scenarios covering traditional, modern, and emerging threats
- β’Based on 8 authoritative sources (NIST, AWS, CISA, OWASP)
- β’GDPR Article 33/34 breach notification requirements (72-hour timeline)
- β’HIPAA Breach Notification Rule guidance (60-day timeline)
- β’NIST Cybersecurity Framework 2.0 function mapping (DE, RS, RC)
- β’Interactive AskUserQuestion workflow for organization customization
- β’Professional Markdown playbook output ready for SOC/CSIRT teams
- β’100% validation pass rate across all scenarios
Available Scenarios:
Traditional Threats (3):
- Ransomware Attack (Critical) - File encryption, lateral movement, backup destruction
- Data Breach / Exfiltration (Critical) - Unauthorized data access and theft
- Phishing / Business Email Compromise (High) - Social engineering and credential theft
Modern & Emerging Threats (3):
- AI/ML Security Incident (High) - Model poisoning, prompt injection, adversarial attacks
- Supply Chain Attack (Critical) - Compromised dependencies, build pipeline injection
- API Security Incident (High) - BOLA/IDOR, broken authentication, rate-limit bypass
Critical Infrastructure & Cloud (3):
- Container/Kubernetes Security (High) - Pod escape, RBAC bypass, malicious images
- IoT/OT Security Incident (Critical) - IoT botnets, SCADA exploitation, ICS disruption
- Cloud Security Breach (Critical) - IAM compromise, misconfigured storage, metadata abuse
Insider & Availability (2):
- Insider Threat (Critical) - Privileged user abuse, data exfiltration, sabotage
- DDoS Attack (High) - Volumetric, protocol, and application-layer attacks
Each Playbook Includes:
- β’Detection & Indicators - Technical and behavioral IOCs mapped to NIST CSF 2.0 (8-9 indicators per scenario)
- β’Response Procedures - Step-by-step actions (Triage β Containment β Eradication) with 15-18 action steps
- β’Recovery Actions - System restoration with validation checklists
- β’Communication Templates - Internal, external, and regulatory notifications
- β’Compliance Guidance - GDPR Article 33/34 and HIPAA Breach Notification Rule
- β’Roles & Responsibilities - Clear team structure and escalation criteria
- β’Post-Incident Activities - Lessons learned and documentation requirements
Quality Metrics (v2.0.0):
- β’8-9 technical indicators per scenario (industry-leading coverage)
- β’5-7 behavioral indicators per scenario
- β’8-9 NIST CSF 2.0 function mappings per scenario
- β’Average playbook size: 412 lines (400-422 range)
- β’100% validation pass rate across all scenarios
Use Cases:
- β’Building your first incident response program
- β’Updating IR playbooks to NIST SP 800-61r3 (April 2025) and modern threats
- β’Preparing for compliance audits (GDPR, HIPAA)
- β’Creating scenario-specific response procedures
- β’Training security operations teams on modern threat landscape
- β’Meeting cyber insurance requirements
- β’Tabletop exercise preparation for diverse threat scenarios
- β’Covering modern threats: AI/ML, supply chain, cloud, API, containers, IoT/OT
Who Should Use:
- β’Security Operations Centers (SOC) and CSIRT teams
- β’Incident Response managers and coordinators
- β’CISOs establishing or modernizing IR programs
- β’Compliance officers (GDPR, HIPAA)
- β’MSPs and MSSPs serving clients
- β’IT managers preparing for security incidents
- β’Organizations in regulated industries (healthcare, finance)
- β’DevSecOps teams managing cloud and container infrastructure
- β’OT/ICS security teams in critical infrastructure sectors
β View Incident Response Playbook Creator Documentation
π Productivity Tools
5. PDF Smart Extractor
Production Ready β’ v2.0.0 β’ NEW: Unified Caching System
Extract and analyze large PDF documents with 99%+ content preservation and 12-115x token reduction. Perfect for technical documentation, compliance frameworks, and research papers that exceed LLM context windows.
October 2025 Updates:
- β’β Password protection support - Interactive prompts + CLI arguments for encrypted PDFs
- β’β Edge case documentation - Shell escaping issues with special characters documented
- β’β Real-world testing - Large encrypted PDFs (140 pages, 8.39MB) successfully extracted
- β’β Security considerations - Passwords never cached, getpass.getpass() for hidden input
Caching Architecture:
- β’Cache location:
~/.claude-cache/pdf/{pdf_name}_{hash}/ - β’Cache key: SHAKE256 hash (SHA-3 family, first 16 chars) ensures unique identification
- β’Cache contents: full_text.txt, pages.json, metadata.json, toc.json, manifest.json
- β’Cache reuse: Instant - no re-extraction needed (unless --force flag used)
- β’Password handling: Passwords NEVER stored in cache (security by design)
- β’Migration: Old SHA-256 caches automatically migrate to SHAKE256 format
Key Features:
- β’Local Extraction - Zero LLM involvement, complete privacy
- β’Semantic Chunking - Intelligent splitting at chapters, sections, paragraphs
- β’12-115x Token Reduction - Load only relevant chunks, not entire documents
- β’Persistent Caching - Extract once, query forever
- β’Password Support - Interactive prompts (recommended) or CLI arguments for encrypted PDFs
- β’Content Preservation - 99.76-99.81% preservation rate
- β’Fast Processing - <2 minutes first extraction, <1 second subsequent queries
- β’PyMuPDF-Powered - Lightweight, reliable PDF parsing with encryption support
Real Performance (Comprehensive Testing - October 2025):
- β’NIST SP 800-161r1 (3.3MB, 325 pages): 215,907 tokens β 1,864 tokens = 115.8x reduction, 99.81% preservation
- β’NIST SP 800-82r3 (8.2MB, 316 pages): 186,348 tokens β 3,085 tokens = 60.2x reduction, 99.76% preservation
- β’Large Technical Book (35.46MB, 414 pages): 110,235 tokens, 400 chunks, 99.81% preservation
- β’Encrypted Document (8.39MB, 140 pages): 260K characters, 65K tokens extracted via Python API
Password Protection Workflow:
# Interactive password prompt (recommended for complex passwords)
python scripts/extract_pdf.py encrypted_document.pdf
# Script prompts: Enter password: [hidden input]
# CLI password argument (for simple passwords or automation)
python scripts/extract_pdf.py encrypted_document.pdf --password YourPassword123
# Python API (for automation with complex passwords)
from extract_pdf import PDFExtractor
extractor = PDFExtractor()
result = extractor.extract_full_pdf('file.pdf', password='complex_P@ssw0rd!')Workflow:
- Extract PDF - One-time local extraction with PyMuPDF (handles encryption)
- Semantic Chunk - Split at intelligent boundaries (chapters, sections)
- Query Efficiently - Search and load only relevant chunks
- Reuse Forever - Cached for instant subsequent queries
Use Cases:
- β’Analyzing NIST, ISO, AWS, Azure, GCP technical documentation
- β’Building knowledge bases from compliance frameworks
- β’Researching academic papers and technical reports
- β’Extracting specific sections from encrypted legal documents
- β’Processing large PDF datasets without token waste
- β’Expanding incident response playbooks (solved "PDF too large" problem)
Who Should Use:
- β’Security researchers analyzing NIST/ISO/CIS frameworks
- β’Compliance officers reviewing regulatory documentation
- β’Developers building RAG systems from PDF sources
- β’Data scientists processing research paper collections
- β’Legal teams working with encrypted contracts and agreements
- β’Anyone working with large technical PDFs (>1MB)
Commands:
# Extract PDF
python scripts/extract_pdf.py document.pdf
# Extract encrypted PDF (interactive)
python scripts/extract_pdf.py encrypted.pdf
# Prompts for password securely
# Extract encrypted PDF (CLI)
python scripts/extract_pdf.py encrypted.pdf --password YourPassword
# Force re-extraction (ignores cache)
python scripts/extract_pdf.py document.pdf --force
# Chunk content
python scripts/semantic_chunker.py {cache_key}
# Search chunks
python scripts/query_pdf.py search {cache_key} "your query"
# List cached PDFs
python scripts/query_pdf.py listSecurity Notes:
- β’β οΈ CLI
--passwordstores password in command history - use interactive prompt for complex passwords - β’β Passwords never stored in cache - only decrypted content
- β’β Cache contains extracted text only - same security model as Adobe, Ghostscript
- β’π See EDGE_CASES_PASSWORDS.md for shell escaping edge cases
β View PDF Smart Extractor Documentation
6. Excel Smart Extractor
Production Ready β’ v2.0.0 β’ Large Workbook Analysis & Unified Caching
Extract and analyze large Excel workbooks (1MB-50MB+) with comprehensive content preservation and 20-100x token reduction. Perfect for compliance matrices, financial models, security audit logs, and data tables that exceed LLM context windows.
Caching Architecture:
- β’Cache location:
~/.claude-cache/xlsx/{workbook_name}_{hash}/ - β’Cache key: SHAKE256 hash (SHA-3 family, first 16 chars) ensures unique identification
- β’Cache contents: full_workbook.json, sheet_{name}.json, named_ranges.json, metadata.json, manifest.json
- β’Cache reuse: Instant - no re-extraction needed (unless --force flag used)
- β’Comprehensive extraction: Formulas, formatting, metadata, named ranges, merged cells
- β’Migration: Old SHA-256 caches automatically migrate to SHAKE256 format
Key Features:
- β’Local Extraction - Zero LLM involvement, complete privacy (openpyxl-powered)
- β’Comprehensive Content Extraction - Formulas, cell formatting, merged cells, hyperlinks, named ranges
- β’20-100x Token Reduction - Load only relevant sheets/columns, not entire workbooks
- β’Persistent Caching - Extract once, query forever
- β’Semantic Chunking - Intelligent splitting by sheets, columns, and row ranges
- β’Fast Processing - <5 seconds first extraction, <1 second subsequent queries
- β’Read-Only Operations - Never modifies source files
Real Performance (Comprehensive Testing - October 2025):
- β’9 real-world files tested (110KB - 1.5MB)
- β’287,460 cells processed across 85 sheets
- β’15,409 formulas extracted including array formulas
- β’Comprehensive extraction including formulas, formatting, and metadata
- β’Token reduction: 4x - 58x (average 27.6x)
Example (Compliance Matrix):
- β’CCM v4.0.12 (Cloud Controls Matrix): 1.41MB, 25 sheets
- β’287K cells β 15K tokens (56.6x reduction)
- β’100% formula preservation including HYPERLINK functions
- β’All control mappings, compliance domains, and audit criteria preserved
Workflow:
- Extract Workbook - One-time local extraction with openpyxl
- Semantic Chunk - Split by sheets, columns, and semantic row ranges
- Query Efficiently - Search and load only relevant sheets/columns
- Reuse Forever - Cached for instant subsequent queries
Use Cases:
- β’Analyzing compliance matrices (ISO 27001, SOC 2, CCM, CAIQ)
- β’Processing financial models and pricing sheets
- β’Extracting security audit logs and analysis reports
- β’Building knowledge bases from Excel data tables
- β’Querying large datasets with complex formulas
Who Should Use:
- β’Compliance officers analyzing security control matrices
- β’Financial analysts working with large pricing models
- β’Security teams processing audit logs in Excel format
- β’Data analysts querying large Excel datasets
- β’Anyone working with Excel files >1MB that exceed LLM context
Commands:
# Extract Excel workbook
python scripts/extract_xlsx.py workbook.xlsx
# Force re-extraction (ignores cache)
python scripts/extract_xlsx.py workbook.xlsx --force
# Chunk content
python scripts/chunk_sheets.py {cache_key}
# Search chunks
python scripts/query_xlsx.py search {cache_key} "your query"
# List cached workbooks
python scripts/query_xlsx.py listSupported Formats:
- β’β .xlsx (Excel 2007+ XML format)
- β’β .xlsm (Macro-enabled workbooks - VBA macros disabled for security)
- β’β .xls (Legacy Excel 97-2003 - convert to .xlsx first)
β View Excel Smart Extractor Documentation
7. Word Smart Extractor
Production Ready β’ v2.0.0 β’ Large Document Analysis & Unified Caching
Extract and analyze large Word documents (1MB-50MB+) with comprehensive content extraction and 10-50x token reduction. Perfect for policy documents, technical reports, contracts, and meeting notes with clear heading structure.
Caching Architecture:
- β’Cache location:
~/.claude-cache/docx/{document_name}_{hash}/ - β’Cache key: SHAKE256 hash (SHA-3 family, first 16 chars) ensures unique identification
- β’Cache contents: full_text.txt, paragraphs.json, tables.json, metadata.json, headings.json, manifest.json
- β’Cache reuse: Instant - no re-extraction needed (unless --force flag used)
- β’Content extraction: Text, tables, formatting, comments, tracked changes, headers/footers
- β’Migration: Old SHA-256 caches automatically migrate to SHAKE256 format
Key Features:
- β’Local Extraction - Zero LLM involvement, complete privacy (python-docx powered)
- β’Comprehensive Content Extraction - Text, tables, formatting, comments, tracked changes
- β’10-50x Token Reduction - Load only relevant sections, not entire documents
- β’Persistent Caching - Extract once, query forever
- β’Semantic Chunking - Intelligent splitting by heading hierarchy (H1, H2, H3)
- β’Fast Processing - 1-5 seconds first extraction, <1 second subsequent queries
- β’Read-Only Operations - Never modifies source files
Real Performance (Tested October 2025):
- β’Small documents (< 50 paragraphs): 5-10x reduction
- β’Medium documents (50-200 paragraphs): 10-30x reduction
- β’Large documents (200+ paragraphs): 30-50x reduction
Example (Security Policy Document):
- β’Acceptable Use Policy: 245 paragraphs, 12 tables
- β’Chunked into 13 semantic sections by heading structure
- β’Each chunk 500-2000 tokens (optimized for LLM context)
- β’Total token reduction: ~25x
Workflow:
- Extract Document - One-time local extraction with python-docx
- Semantic Chunk - Split by heading hierarchy (H1, H2, H3 boundaries)
- Query Efficiently - Search and load only relevant sections
- Reuse Forever - Cached for instant subsequent queries
Use Cases:
- β’Analyzing policy documents (security, privacy, compliance)
- β’Processing technical reports and specifications
- β’Contract review and analysis
- β’Meeting notes and project documentation
- β’Building knowledge bases from Word documents
Who Should Use:
- β’Security teams analyzing policy documents
- β’Compliance officers reviewing contract terms
- β’Technical writers working with large specifications
- β’Legal teams processing contracts and agreements
- β’Anyone working with Word documents >1MB
Commands:
# Extract Word document
python scripts/extract_docx.py document.docx
# Force re-extraction (ignores cache)
python scripts/extract_docx.py document.docx --force
# Chunk content by headings
python scripts/semantic_chunker.py {cache_key}
# Search chunks
python scripts/query_docx.py search {cache_key} "your query"
# Get specific heading section
python scripts/query_docx.py heading {cache_key} "Section Title"
# List cached documents
python scripts/query_docx.py listSupported Formats:
- β’β .docx (Word 2007+ XML format)
- β’β .docm (Macro-enabled Word documents - VBA macros not extracted by design)
- β’β .doc (Legacy Word 97-2003 - convert to .docx first)
- β’β Password-protected files (cannot be opened)
β View Word Smart Extractor Documentation
π Caching Architecture
All three Smart Extractor plugins share the same efficient caching architecture:
First Extraction (One-Time Process):
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β 1. User runs extract script with document path β
β 2. Plugin generates SHAKE256 hash of document (SHA-3) β
β 3. Creates cache directory: ~/.claude-cache/{type}/{name}_{hash}/ β
β 4. Extracts content locally (PyMuPDF/openpyxl/python-docx) β
β 5. Saves structured JSON + full text to cache β
β 6. Returns cache key for future queries β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β
Subsequent Queries (Instant):
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β 1. User queries with cache key β
β 2. Plugin reads cached JSON (no re-extraction) β
β 3. Chunks content semantically (chapters/sheets/headings) β
β 4. Loads only relevant chunks (10-100x token reduction) β
β 5. Returns precise results in <1 second β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββCache Benefits:
- β’β Extract once, query forever - No re-processing needed
- β’β Instant queries - <1 second for cached documents
- β’β Token optimization - 10-100x reduction by loading only relevant chunks
- β’β Complete privacy - All processing happens locally, no external API calls
- β’β Persistent storage - Cache survives Claude Code restarts
- β’β Automatic invalidation - Document changes detected via SHAKE256 hash (SHA-3 family)
- β’β Automatic migration - Old SHA-256 caches automatically migrate to SHAKE256 format
Cache Locations (v2.0.0 Unified):
- β’PDF:
~/.claude-cache/pdf/{pdf_name}_{hash}/ - β’Excel:
~/.claude-cache/xlsx/{workbook_name}_{hash}/ - β’Word:
~/.claude-cache/docx/{document_name}_{hash}/
Cache Management:
# Force re-extraction (bypass cache)
python scripts/extract_{pdf|xlsx|docx}.py document.{pdf|xlsx|docx} --force
# List all cached documents
python scripts/query_{pdf|xlsx|docx}.py list
# View cache statistics
python scripts/query_{pdf|xlsx|docx}.py stats {cache_key}
# Clear specific cache (v2.0.0 paths)
rm -rf ~/.claude-cache/{pdf|xlsx|docx}/{cache_key}/
# Clear all caches for one type
rm -rf ~/.claude-cache/{pdf|xlsx|docx}/
# Clear all caches (all three types)
rm -rf ~/.claude-cache/π‘ Request New Plugins or Report Issues
We welcome community feedback, bug reports, and plugin ideas!
π Request a New Plugin
Have an idea for a security, compliance, or productivity plugin?
[β Open a Feature Request](https://github.com/diegocconsolini/ClaudeSkillCollection/issues/new?labels=enhancement&template=feature_request.md)
Good plugin ideas:
- β’Based on authoritative sources (regulations, frameworks, standards)
- β’Produces tangible deliverables (reports, documents, policies)
- β’Solves a specific security/compliance/productivity problem
- β’Can work with static files (no live system access required)
Examples of plugins we'd love to see:
- β’CCPA Compliance Auditor (California privacy law)
- β’HIPAA Privacy Auditor (Healthcare compliance)
- β’OWASP Top 10 Scanner (Web security)
- β’Privacy Policy Generator (GDPR/CCPA-compliant)
- β’Container Security Scanner (Docker/Kubernetes)
π Report Bugs
Found a bug in an existing plugin?
[β Open a Bug Report](https://github.com/diegocconsolini/ClaudeSkillCollection/issues/new?labels=bug&template=bug_report.md)
Please include:
- Plugin name and version
- Claude Code version
- Steps to reproduce
- Expected vs actual behavior
- Relevant code snippets (sanitized - no sensitive data)
π¬ Suggest Improvements
Have ideas for improving existing plugins?
[β Start a Discussion](https://github.com/diegocconsolini/ClaudeSkillCollection/discussions)
Examples:
- β’Additional policy templates for Policy Generator
- β’New incident scenarios for IR Playbook Creator
- β’Performance improvements for Smart Extractors
- β’Additional compliance framework mappings
π¦ Installation
Prerequisites
- β’Claude Code (latest version recommended)
- β’Python 3.8+ (for automated tools and scripts)
- β’Git (for repository cloning)
Plugin-Specific Dependencies
Some plugins require additional Python libraries. Each plugin includes a requirements.txt file for easy installation:
- β’PDF Smart Extractor - Requires
pymupdfβ’ Installation Guide - β’Excel Smart Extractor - Requires
openpyxl,pandasβ’ Installation Guide - β’Word Smart Extractor - Requires
python-docxβ’ Installation Guide
Installation methods:
- Virtual environment (recommended): Creates isolated Python environment
- System-wide installation: Installs for all users
See individual plugin READMEs for detailed instructions and troubleshooting.
Option 1: Plugin Marketplace (Recommended)
# Add the Security & Compliance Marketplace
/plugin marketplace add diegocconsolini/ClaudeSkillCollection
# Browse available plugins
/plugin list
# Install specific plugins
/plugin install gdpr-auditor@security-compliance-marketplace
/plugin install cybersecurity-policy-generator@security-compliance-marketplace
/plugin install pdf-smart-extractor@security-compliance-marketplace
# Update installed plugins
/plugin updateBenefits:
- β’β One-command installation
- β’β Automatic updates
- β’β Easy plugin management
- β’β Version tracking
Option 2: Manual Installation
# Navigate to Claude plugins directory
cd ~/.claude/plugins/
# Clone repository
git clone https://github.com/diegocconsolini/ClaudeSkillCollection.git
# Symlink desired plugins
ln -s ClaudeSkillCollection/gdpr-auditor ./gdpr-auditor
ln -s ClaudeSkillCollection/pdf-smart-extractor ./pdf-smart-extractor
# Restart Claude CodeVerification
Test that plugins are loaded:
For GDPR Auditor:
"Can you help me audit my application for GDPR compliance?"For PDF Smart Extractor:
"Extract this large PDF: /path/to/technical_doc.pdf"π How Plugins Work
Claude Code plugins are specialized prompts with supporting materials that give Claude domain expertise:
- Automatic Loading - Mention the plugin's domain or use explicit commands
- Context Injection - Claude loads plugin knowledge and workflows
- Tool Access - Claude uses plugin-specific scripts and reference materials
- Guided Workflow - Claude follows systematic methodology for thorough analysis
Example: GDPR Auditor Workflow
User: "Audit my app for GDPR compliance"
β
Claude loads gdpr-auditor plugin
β
Plugin guides Claude through:
1. Identify scope and personal data types
2. Run automated code scanners
3. Consult GDPR reference materials (EUR-Lex, ICO, EDPB)
4. Analyze code and configurations
5. Generate compliance audit report with article references
β
Professional audit report with specific findingsExample: PDF Smart Extractor Workflow
User: "Extract this 10MB PDF: nist_sp_800-161.pdf"
β
Claude loads pdf-smart-extractor plugin
β
Plugin guides Claude through:
1. Run extract_pdf.py script (local PyMuPDF extraction)
2. Generate SHAKE256 cache key (SHA-3 family)
3. Save to ~/.claude-cache/pdf/{name}_{hash}/
4. Run semantic_chunker.py (chapter/section splitting)
5. Return cache key for future queries
β
User can now query: "Search for 'supply chain risk' in cached PDF"
β
Plugin uses query_pdf.py to search chunks (instant, <1 second)ποΈ Repository Structure
ClaudeSkillCollection/
βββ README.md # This file
βββ LICENSE # MIT License
βββ CONTRIBUTING.md # Contribution guidelines
βββ PLUGIN_STRUCTURE_GUIDE.md # Official plugin development guide
βββ CHANGELOG.md # Version history
β
βββ .claude-plugin/ # Marketplace configuration
β βββ marketplace.json # Plugin catalog (9 plugins)
β
βββ plugin-security-checker/ # Plugin Security Checker v3.0.0
β βββ README.md
β βββ plugin.json
β βββ agents/plugin-security-checker.md # Agent with YAML frontmatter
β βββ scripts/ # 91 specialized pattern detection agents
β β βββ intelligent_orchestrator.py # Consensus voting engine
β β βββ accuracy_cache.py # Shared learning with Bloom+Trie
β β βββ pattern_agent.py # Base agent class
β β βββ scan_plugin.py # Main scanner
β β βββ generate_report.py # Report generation
β βββ references/ # Pattern databases and CVE mappings
β β βββ dangerous_functions_expanded.json # 91 patterns
β βββ examples/
β
βββ gdpr-auditor/ # GDPR Compliance Auditor
β βββ README.md
β βββ plugin.json
β βββ agents/gdpr-auditor.md # Agent with YAML frontmatter
β βββ scripts/ # 5 automated scanning tools
β βββ references/ # 8 GDPR reference documents (EUR-Lex, ICO, EDPB)
β βββ examples/
β
βββ incident-response-playbook-creator/ # IR Playbook Generator v2.0.0
β βββ README.md
β βββ CHANGELOG.md # v2.0.0 release notes
β βββ plugin.json
β βββ SKILL.md # Agent with YAML frontmatter
β βββ scripts/ # Playbook generation scripts
β β βββ browse_scenarios.py # Browse 11 scenarios
β β βββ generate_playbook_markdown.py # Generate playbooks
β βββ references/ # 288KB NIST/AWS/CISA/OWASP data
β β βββ incident_scenarios_v2.json # 11 scenarios (58KB, master file)
β β βββ incident_scenarios_simplified.json # Legacy 4 scenarios
β β βββ framework_mappings.json
β β βββ communication_templates.json
β βββ output/ # Generated playbooks
β βββ examples/
β
βββ pdf-smart-extractor/ # PDF Smart Extractor (v2.0.0)
β βββ README.md
β βββ plugin.json
β βββ agents/pdf-smart-extractor.md
β βββ scripts/ # extract, chunk, query scripts
β βββ test-files/ # Test PDFs
β βββ TEST_RESULTS.md # Comprehensive test report
β βββ EDGE_CASES_PASSWORDS.md # Password protection edge cases
β βββ PASSWORD_PROTECTION_TEST_LOG.md
β
βββ xlsx-smart-extractor/ # Excel Smart Extractor (v2.0.0)
β βββ README.md
β βββ plugin.json
β βββ agents/xlsx-smart-extractor.md
β βββ scripts/ # extract, chunk, query scripts
β βββ test-files/ # Test Excel files
β βββ TEST_RESULTS.md # Comprehensive test report
β
βββ docx-smart-extractor/ # Word Smart Extractor (v2.0.0)
β βββ README.md
β βββ plugin.json
β βββ agents/docx-smart-extractor.md
β βββ scripts/ # extract, chunk, query scripts
β βββ examples/
β
βββ security-report-builder/ # Security Report Builder (v1.0.1)
β βββ README.md
β βββ .claude-plugin/plugin.json
β βββ agents/security-report-builder.md
β βββ scripts/ # Report generation scripts
β βββ templates/ # Report templates
β
βββ chrome-devtools-optimizer/ # Chrome DevTools Optimizer (v1.0.1)
β βββ README.md
β βββ .claude-plugin/plugin.json
β βββ agents/chrome-devtools-optimizer.md
β βββ scripts/ # Gemini Flash integration
β βββ references/ # Tool reference, token costs
β βββ patterns/ # Navigation, forms, debugging patterns
β
βββ private/wip-plugins/ # Private development workspace
β βββ cybersecurity-policy-generator/ # Policy Generator (in beta)
β βββ README.md
β βββ plugin.json
β βββ agents/cybersecurity-policy-generator.md
β βββ scripts/ # 4 policy generation scripts
β βββ references/ # 320KB SANS/CIS templates
β βββ output/ # Generated policies
β
βββ .github/ # GitHub templates
βββ ISSUE_TEMPLATE/
βββ feature_request.md
βββ bug_report.mdβ Quality Standards
All plugins in this marketplace meet professional quality standards:
Documentation
- β’β Comprehensive README with clear instructions
- β’β Detailed usage examples and workflows
- β’β Technical specifications and requirements
- β’β Reference materials from authoritative sources
Code Quality
- β’β Production-ready Python scripts with error handling
- β’β Type hints and comprehensive docstrings
- β’β Defensive security practices only
- β’β Tested on real-world projects (October 2025: 35MB PDFs, 1.5MB Excel files, complex Word documents)
- β’β Follows Claude Code plugin best practices (PLUGIN_STRUCTURE_GUIDE.md)
- β’β Comprehensive test suites with edge case coverage
- β’β YAML frontmatter in all agent files (required for marketplace loading)
Accuracy & Compliance
- β’β Information verified against primary sources
- GDPR Auditor: EUR-Lex official GDPR text, ICO guidance, EDPB guidelines - Policy Generator: SANS policy templates, CIS Controls v8, ISO 27001, NIST CSF - IR Playbook Creator: NIST SP 800-61r3 (April 2025), CISA playbooks, GDPR/HIPAA official texts
- β’β No hallucinated facts or unverified claims
- β’β Regular updates to reflect current standards
- β’β Clear version tracking and changelog
Plugin Design Principles
- β’β Produces tangible deliverables (reports, documents, policies)
- β’β Works with static files (no live system scanning)
- β’β Based on objective criteria (regulations, standards, frameworks)
- β’β Includes comprehensive reference materials
- β’β Follows systematic, reproducible workflows
πΊοΈ Roadmap
Upcoming Plugins
Data Privacy & Security:
- β’[ ] CCPA Compliance Auditor - California Consumer Privacy Act compliance
- β’[ ] HIPAA Privacy Auditor - Healthcare privacy and security compliance
- β’[ ] PCI DSS Auditor - Payment Card Industry security standards
Security Assessment:
- β’[ ] OWASP Top 10 Scanner - Web application security vulnerability analysis
- β’[ ] API Security Auditor - REST/GraphQL security assessment
- β’[ ] Container Security Scanner - Docker and Kubernetes security audit
Governance & Documentation:
- β’[ ] Privacy Policy Generator - GDPR, CCPA-compliant privacy policies
- β’[ ] Security Documentation Generator - Technical security documentation
- β’[ ] Compliance Evidence Generator - Audit evidence and attestations
[β Vote for next plugins](https://github.com/diegocconsolini/ClaudeSkillCollection/issues) or suggest new ones!
π€ Contributing
We welcome contributions from the security and compliance community!
Ways to Contribute:
- β’Report bugs or suggest improvements
- β’Enhance existing plugins
- β’Create new plugins
- β’Improve documentation
- β’Share usage examples
Contribution Process:
- Review CONTRIBUTING.md for guidelines
- Check existing issues and pull requests
- Follow plugin quality standards
- Submit pull request with clear description
Plugin Submission Checklist:
- β’[ ] Agent file with YAML frontmatter (description + capabilities)
- β’[ ] Production-ready scripts with error handling
- β’[ ] Reference materials from authoritative sources
- β’[ ] Complete README with installation and usage guide
- β’[ ] Working examples and test cases
- β’[ ] Follows defensive security principles
- β’[ ] No malicious code or unethical use cases
π Support
Getting Help:
- β’Documentation: Check plugin README files and PLUGIN_STRUCTURE_GUIDE.md
- β’Issues: Open a GitHub issue
- β’Discussions: Join GitHub Discussions
Reporting Issues:
Please include:
- Claude Code version
- Plugin name and version
- Steps to reproduce
- Expected vs actual behavior
- Relevant code snippets (sanitized - no sensitive data)
π License
MIT License - See LICENSE for details
What this means:
- β’β Free for commercial use
- β’β Modify and distribute freely
- β’β Private use allowed
- β’β οΈ No warranty provided
- β’β οΈ Must include original license and copyright notice
β οΈ Disclaimer
These plugins are analysis tools - they do not replace professional advice:
- β’Legal Compliance: Consult qualified legal counsel for compliance matters
- β’Security Audits: Professional security assessments still recommended
- β’Privacy Assessments: Work with certified privacy professionals
- β’Framework Certification: Plugins support but don't guarantee certification
Accuracy:
- β’Plugins provide guidance based on current information
- β’Regulations and standards change over time
- β’Always verify findings with authoritative sources
- β’No liability for errors, omissions, or consequences of use
Ethical Use Only: All plugins are designed for defensive security purposes:
- β’β Identifying vulnerabilities to remediate them
- β’β Improving compliance and security posture
- β’β Protecting user privacy and data
- β’β NOT for exploitation, malicious use, or unethical purposes
π Changelog
Version 2.1.0 (2025-12-17)
New Plugins:
- β’Released Chrome DevTools Optimizer v1.0.1
- Reduce token consumption by 70-80% when using Chrome DevTools MCP - Smart snapshot-first strategy (text over images) - Optional Gemini Flash integration for visual analysis (~$0.001/image vs $0.005) - Decision trees, pattern guides for navigation, forms, debugging, visual checks - Interactive setup wizard for Gemini API key
- β’Released Security Report Builder v1.0.1
- Professional security report generator with HTML, PDF, and DOCX output - Context-aware analysis to reduce false positives - MITRE ATT&CK framework mapping
Plugin Fixes:
- β’Fixed all 9 plugin manifests for Claude Code compatibility
- Changed agents format from string to array: "./agents/" β ["agents/name.md"] - Removed unsupported keys: $schema, category, requirements, scripts - Moved plugin.json to .claude-plugin/ directory where needed
Marketplace Updates:
- β’Updated marketplace to 9 total plugins (was 8)
- β’Version bump to 2.1.0
Version 2.0.0 (2025-10-24)
New Plugin Release:
- β’Released Plugin Security Checker v3.0.0
- 91 specialized pattern detection agents (17 CRITICAL, 39 HIGH, 23 MEDIUM, 2 LOW) - IntelligentOrchestrator with consensus voting and conflict resolution - AccuracyCache with Bloom filter + Trie hybrid (zero false positives) - MITRE ATT&CK/ATLAS framework mapping for attack technique identification - Real-world testing: Scanned 987 plugins from 15 marketplaces (100% success rate) - Security results: 3 CRITICAL, 1 HIGH, 982 LOW risk plugins identified - Test coverage: 29/29 tests passed (100%) - Adaptive learning with auto-evolving rules from validated detections - CVE mapping: CVE-2025-52882, CVE-2025-54794, CVE-2025-54795, CVE-2025-59828 - OWASP API Top 10 2023 mappings
Marketplace Updates:
- β’Updated marketplace to 7 total plugins
- β’Enhanced marketplace description with plugin security scanning capabilities
Version 2.0.0-extractors (2025-10-21)
Unified Caching System - Breaking Internal Changes, Zero User Impact:
- β’NEW: Shared
smart_cache.pylibrary for all smart-extractors
- SHAKE256 hashing (SHA-3 family) replaces SHA-256 - Unified cache location: ~/.claude-cache/{doc_type}/ (was ~/.claude-{type}-cache/) - Automatic SHA-256 β SHAKE256 cache migration (transparent to users) - Comprehensive documentation in /shared/CACHE_STRATEGY.md and /shared/CHANGELOG.md
Extractor Updates:
- β’PDF Smart Extractor v2.0.0 - Unified caching, tested with 316-page documents (8.2MB)
- β’Excel Smart Extractor v2.0.0 - Unified caching, tested with 19K cell workbooks
- β’Word Smart Extractor v2.0.0 - Unified caching, tested with policy documents
Technical Improvements:
- β’Zero external dependencies for caching (Python stdlib only)
- β’Bloom filter support for O(1) cache existence checks (optional)
- β’Future-ready for environment variable configuration (v2.1.0)
- β’LaTeX migration: Old caches automatically migrate on first access
User Impact:
- β’β Zero breaking changes - everything works as before
- β’β Automatic cache migration - no manual action needed
- β’β
Cleaner home directory - one
.claude-cache/instead of three separate dirs
Version 1.5.0 (2025-10-20)
New Plugins:
- β’Released Excel Smart Extractor v1.0.0
- 100%+ content preservation (formulas, formatting, metadata) - 20-100x token reduction through semantic chunking - Tested with 9 real-world files (287K cells, 15K formulas) - Persistent caching in ~/.claude-xlsx-cache/
- β’Released Word Smart Extractor v1.0.0
- Complete content extraction (text, tables, formatting, comments) - 10-50x token reduction through heading-based chunking - Tested with security policy documents - Persistent caching in ~/.claude-docx-cache/
Updates:
- β’PDF Smart Extractor upgraded to v1.1.0
- Added password protection support (interactive + CLI) - Edge case documentation for shell escaping - Real-world testing with large encrypted PDFs (8.39MB, 140 pages)
- β’Updated marketplace to 6 total plugins
- β’Enhanced README with categorization, caching architecture, GitHub issues invitation
Version 2.1.0 (2025-10-22)
Major Plugin Update:
- β’Incident Response Playbook Creator upgraded to v2.0.0
- Expanded from 4 to 11 comprehensive incident scenarios (175% increase) - Added 7 new scenarios: Supply Chain, Container/K8s, IoT/OT, Cloud, API, Insider, DDoS - Enhanced original 4 scenarios with improved quality metrics - Based on 8 authoritative sources (NIST, AWS, CISA, OWASP) - 288KB total reference data (incident_scenarios_v2.json: 58KB, 11 scenarios) - All scenarios pass quality validation (100% success rate) - Critical bug fix: Added missing eradication field in data_breach scenario - Quality improvements: 8-9 technical indicators, 5-7 behavioral indicators, 8-9 NIST CSF IDs per scenario - Average playbook size: 412 lines (400-422 range)
Version 1.3.0 (2025-10-19)
New Plugin Release:
- β’Released Incident Response Playbook Creator v1.0.0
- Based on NIST SP 800-61r3 (April 2025) - 4 incident scenarios with GDPR/HIPAA compliance - 110KB authoritative reference data
- β’Updated repository documentation
Version 1.1.0 (2025-10-19)
New Plugin Release:
- β’Released Cybersecurity Policy Generator v1.0.0
- 51 professional policy templates (SANS + CIS Controls) - 320KB reference data with compliance framework mappings - Interactive AskUserQuestion workflow - Multi-format generation (Markdown, Word, HTML, PDF) - Production-tested with real organization (Guatemaltek)
Version 1.0.0 (2025-10-18)
Initial Release:
- β’Released GDPR Auditor v1.0.0
- 8 comprehensive GDPR reference documents - 5 automated static code scanning tools - Complete compliance audit workflow
- β’Released PDF Smart Extractor v1.0.0
- 100% content preservation with PyMuPDF - 12-115x token reduction - Persistent caching architecture - Tested with NIST documents up to 35MB
Acknowledgments
Data Sources:
- β’GDPR Auditor: EUR-Lex (Official EU Law), ICO Guidance, EDPB Guidelines
- β’Policy Generator: SANS Institute Policy Templates, CIS Controls v8, ISO 27001, NIST CSF, SOC 2 Trust Service Criteria
- β’IR Playbook Creator: NIST SP 800-61r3, NIST CSF 2.0, CISA Playbooks, GDPR Articles 33/34, HIPAA Breach Notification Rule
- β’Smart Extractors: PyMuPDF, openpyxl, python-docx (open-source libraries)
Community: Thanks to all contributors, testers, and users who help improve these plugins!
Security & Compliance Marketplace - Professional plugins for Claude Code
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/gdpr-auditor.md https://raw.githubusercontent.com/diegocconsolini/ClaudeSkillCollection/main/SKILL.md/gdpr-auditorFrequently Asked Questions
What is gdpr-auditor?
Comprehensive GDPR compliance auditing plugin that analyzes static code files, database schemas, and configurations for EU data protection regulation compliance. Includes 8 reference documents, 5 automated scanning tools, and generates detailed compliance audit reports.
How to install gdpr-auditor?
To install gdpr-auditor, create the .claude/skills directory in your project, then run the curl command to download the skill file. Once installed, invoke it in Claude Code with /gdpr-auditor.
What is gdpr-auditor best for?
gdpr-auditor is a community categorized under General. It is designed for: documentation, plugin, gdpr, compliance, privacy, data-protection, eu-regulation, audit. Created by Diego Consolini.