11 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 11 plugins that match these filters.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceAnalyzes how multiple regulations interact for a specific product, service, or business model. Identifies where obligations overlap, reinforce, complement, duplicate, or conflict; builds a priority matrix; produces an integrated compliance timeline; and estimates the total compliance burden. Use when (1) scoping a new product or service against the full regulatory landscape before launch, (2) conducting M&A due diligence on a target's multi-regulation exposure, (3) building a strategic compliance roadmap where single-regulation analyses miss the interactions, (4) advising on complex situations where regulations touch the same conduct from different angles, or (5) estimating budget and resourcing for multi-regulation compliance. Primary coverage of EU digital regulation (GDPR, Data Act, AI Act, CRA, NIS2, DORA, DMA, DSA, ePrivacy) and national implementations; the framework extends to any jurisdiction where overlapping regulatory regimes apply to the same activity.
Generates standalone interactive HTML "deal cards" that translate complex regulations into negotiation-ready reference tools, systematically distinguishing mandatory obligations from negotiable implementation choices. Use when the user needs an interactive regulatory guide for (1) contract negotiation support, (2) client education or internal training, (3) regulatory briefings for commercial stakeholders, or (4) structured comparison between required and flexible compliance paths. Primary focus on EU digital regulation (Data Act, AI Act, CRA, DORA, NIS2, GDPR) but the structural pattern transfers to any regulation where separating hard obligations from implementation choice is the point. Supports bilingual output where the jurisdiction calls for it.
Framework for assessing IT service providers, technology vendors, and third-party partners. Creates structured risk assessments across financial, operational, compliance, security, and reputational dimensions with regulatory checklists (GDPR, DORA, NIS2, SOX). Use when: (1) Evaluating new vendors or technology providers, (2) Conducting third-party risk assessments for procurement, (3) Performing critical vendor due diligence for regulatory compliance, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring processes, (6) Assessing vendor concentration risk, or (7) Generating executive-level vendor risk reports.
Structured NIS2 compliance assessment covering scope classification (Annex I/II, size thresholds, DORA/CIR checks), gap analysis across all 10 Art. 21 risk management measures with 0–4 maturity scoring and ISO 27001 references, and a prioritized compliance roadmap. Deep German BSIG-neu coverage (BSI registration, § 30/32/38, incident reporting, Nachweispflicht) plus high-level jurisdiction profiles for Italy, France, Netherlands, Austria, and Spain. Built on ENISA guidance and BSI #nis2know packages.
Operacje RODO i cyber dla kancelarii i IOD (5 skilli): ocena skutkow DPIA (art. 35-36), obsluga naruszenia w 72h (art. 33-34), zadania osob DSAR (art. 12, 15-22), rejestr czynnosci RoPA i przeglad umow powierzenia DPA (art. 30, 28), triage NIS2/KSC (zakres, 10 srodkow art. 21, zegar raportowania). Grounding cytatu decyzji UODO zyje w orzecznictwo-zrodla (uodo-grounding-pl). Ugruntowane w artykulach RODO/NIS2 i wytycznych EROD/UODO. Bez konektorow, bez wlasnych polaczen wychodzacych.
Serious Incident Reporting (SIR) for high-risk AI systems under Article 73 EU AI Act (Regulation (EU) 2024/1689). Assess, qualify, draft, and submit Art. 73 SIR notifications across the four Art. 3(49) harm categories (death or serious health damage, critical infrastructure disruption, breach of fundamental rights, property or environmental damage). Covers Art. 73 immediate, 2/10/15-day reporting windows, market surveillance authority notification, deployer duties under Art. 26(5), and cross-regulation mapping with GDPR Art. 33/34 breach notification, NIS2 Art. 23 incident reporting, DORA Art. 19 ICT incident, and MDR vigilance. Built for in-house counsel and AI risk teams handling AI incidents, building AI incident response playbooks, or managing AI failure, AI bias, or automated decision incidents. DACH routing through German market surveillance (BNetzA, BaFin, BSI, BfArM, KBA). Pairs with the EU AI Act System Classifier, High-Risk Readiness, FRIA, and GPAI Code of Practice skills.
Cited EU Cyber Resilience Act assessment for a product with digital elements: scope, product classification, role-specific vulnerability-handling duties, and Article 14 reporting - joined with live CVE / CISA-KEV / EPSS vulnerability intelligence, and a NIS2 / GDPR / DORA entity-level screen. Requires the free Ansvar Gateway MCP connector; every legal claim is fetched from official publisher text at answer time and cited, never answered from model memory.
One security incident can trigger several EU reporting regimes at once. This skill screens NIS2, GDPR, DORA, and the Cyber Resilience Act for each involved legal entity, applies the served trigger tests, checks each duty was actually in force for the incident, resolves the receiving authority per regime and member state from served national law (e.g. Dutch and German transpositions), and produces a deadline table in which every duty, authority, and deadline is quoted and cited from official publisher text. Requires the free Ansvar Gateway MCP connector; never answers from model memory - a connector failure is never converted into "no duty exists".
EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security (Art. 21(2)(d); coordinated risk assessments Art. 22), gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis. Also covers Commission Implementing Regulation (EU) 2024/2690, the technical/methodological sub-requirements for Art. 21(2) and the significant-incident thresholds binding on DNS/cloud/data-centre/MSP/MSSP/trust-service and other digital entities. Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences between essential and important entities, and cross-border coordination.
Conseiller expert en conformité PCI DSS v4.0.1 (seule version active depuis le 31 décembre 2024). Utiliser pour toute question sur PCI DSS, la sécurité des paiements par carte, les données de titulaires, le périmètre du CDE, les types de SAQ (A, A-EP, B, B-IP, C, C-VT, P2PE, D), le ROC, l'AOC, les évaluations QSA, les scans ASV, les niveaux de marchands et de prestataires, la segmentation réseau, les tests d'intrusion, la tokenisation, le chiffrement du PAN, ou l'une des 12 exigences. Couvre la révision SAQ A de janvier 2025 (critère d'éligibilité r1, FAQ 1588), les exigences v4.0 obligatoires depuis le 31 mars 2025, et l'articulation avec DSP2, RGPD, NIS2 et DORA via les connecteurs MCP LibreJustice et EUR-Lex. Déclencheurs : « sommes-nous conformes PCI ? », « quel SAQ s'applique ? », « qu'est-ce qui a changé en v4.0 ? », « comment préparer un audit QSA ? ».
Runs a server-enforced STRIDE threat model and LINDDUN privacy threat model over a system described in prose, screens named dependencies against live CVE/KEV/EPSS data, and builds a cited screen of which EU security obligations (GDPR, NIS2, CRA, AI Act) may apply and which need determination - every regulatory statement fetched from officially published text through the Ansvar Gateway connector at answer time, with scope, role, and application-date limits stated. Never answered from model memory; never a compliance verdict.
