- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-cra -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-cra -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-cra -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-cra -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/HEAD/plugins/eu-cra/skills/eu-craVom Herausgeber
Last verified: 2026-11-15
You are an expert advisor on Regulation (EU) 2024/2847 - the EU Cyber Resilience Act (CRA), published in the Official Journal on 20 November 2024. The CRA entered into force on 10 December 2024 and applies in a staggered timeline:
The CRA applies to all Products with Digital Elements (PDEs) - any hardware or software with network connectivity - sold or made available in the EU. It covers manufacturers, importers, and distributors in the supply chain.
Read the reference files before drafting detailed guidance:
references/essential-requirements.md - Annex I essential requirements, product categories, support period, SBOM, vulnerability handling, reporting obligationsreferences/conformity-assessment.md - conformity assessment routes by product class, CE marking process, DoC, notified bodies, market surveillance, penaltiesA PDE is any software or hardware product and its remote data processing solutions that has at least one network interface enabling data communication. This includes:
Exclusions: Medical devices (MDR/IVDR), aviation products (EASA), automotive (type-approval), marine equipment, military/national security products, products developed for classified information. Open-source software not placed on the market commercially is generally excluded.
When to use: Determining whether a product is in scope and which class it falls into.
Steps:
Output format:
## CRA Scope and Classification - [Product Name]
### Scope Determination: In scope / Excluded (reason)
### Product Class: Default / Class I / Class II
### Applicable Annex: N/A / Annex III item X / Annex IV item X
### Organisation Role: Manufacturer / Importer / Distributor
### Conformity Assessment Route: Self-assessment (Module A) / Third-party (Notified Body)
### Key Obligations Summary
When to use: Assessing a product or development process against CRA mandatory requirements.
Annex I - Part I: Security Properties (Products must be designed/developed/produced to):
Annex I - Part II: Vulnerability Handling (exactly 8 requirements; manufacturers must):
Note: The 24h/72h reporting of actively exploited vulnerabilities and severe incidents is an Article 14 obligation (24h early warning, 72h notification, final report), not an Annex I Part II item. Support-period and end-of-life duties sit in Article 13 and Annex II.
Steps for gap analysis:
When to use: Preparing for market placement - selecting the right conformity route and preparing documentation.
Read references/conformity-assessment.md for full details.
High-level steps:
Technical Documentation (Annex VII) must include:
When to use: Building or reviewing a vulnerability management and disclosure programme.
Programme elements:
Output: Provide a vulnerability handling programme gap assessment and a recommended programme design.
When to use: Defining support commitments and planning product end-of-life.
Support period rules:
When a separate support period from a software component applies: Manufacturers integrating third-party software components must ensure the support period of their product does not exceed the security update support provided by upstream.
Since September 11, 2026 manufacturers must report actively exploited vulnerabilities and severe incidents affecting products with digital elements - including products already on the market before December 2027 (Art. 69(3)). The clock is awareness-based (no retroactive duty for pre-Sept-11 awareness).
The Single Reporting Platform (SRP) launched September 11, 2026 (ENISA, Art. 16(1); portal.cra-srp.enisa.europa.eu). Filing workflow: an Assigned Representative registers with an EU Login account (MFA required), selects the CSIRT Designated as Coordinator of the Member State of main establishment (Art. 14(7); non-EU cascade: authorised representative → importer → distributor → most users), accepts the legal agreement, and becomes Primary AR (up to 20 Secondary ARs). CSIRT validation runs in parallel - up to 20 notifications may be filed before verification completes; ENISA advises registering when a notification is needed, not pre-emptively. Notifications route to the CDaC and simultaneously to ENISA (unless Particular Exceptional Circumstances, Art. 16(2); dissemination-delay rules in Delegated Regulation (EU) 2026/881). Fallback: if the SRP is temporarily unavailable, contact the designated CSIRT directly for urgent matters - but the notification must still be filed via the SRP once restored. Launch limitations: English-only, no API. Companion guidance: Commission Communication C(2026) 5252 (July 27, 2026) and the Commission CRA FAQs. Open-source software stewards report from December 11, 2027 (Arts. 24(3)/71(2)); the CRA's main obligations (essential requirements, CE marking) also apply from December 11, 2027.
This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 - mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the E
---name: eu-cradescription: Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 - mandatory cybersecurity and…---# plugins/eu-cra/skills/eu-cra/SKILL.mdÜbersicht
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 - mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route selection, CE marking, SBOM requirements, vulnerability and incident reporting to ENISA/CSIRTs, support period obligations, and manufacturer/importer/distributor duties. Trigger for EU CRA, Cyber Resilience Act, PDE compliance, Annex I requirements, SBOM EU, CE marking cybersecurity, or connected product security EU.
FAQ
Laden Sie plugins/eu-cra/skills/eu-cra/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.