eu-cra
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.
Install / Use
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-craInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of eu-cra
eu-cra scores 89/100 on our quality scale, 553rd of 1,108 Security skills we index (top 50%).
Its SKILL.md is 16 KB long, well organised into 23 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has 916 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so eu-cra is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
eu-cra compared with similar skills
All 4 of these similar skills score higher than eu-cra; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| eu-cra (this skill)by Sushegaad | 89 | 916 | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install eu-cra?
- Run
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-cra. The install tabs above show the steps for each supported agent. - Which AI agents does eu-cra work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is eu-cra safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is eu-cra still maintained?
- The repository was last updated about 2 months ago, so eu-cra is actively maintained.
Skill content
View source on GitHubname: eu-cra description: "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."
EU Cyber Resilience Act (CRA) Skill
Last verified: 2026-09-14
Overview
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:
| Milestone | Date | |---|---| | Entry into force | 10 December 2024 | | Vulnerability & incident reporting obligations | 11 September 2026 — NOW IN FORCE | | Notified body obligations | 11 December 2026 | | Full application (all obligations) | 11 December 2027 |
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, penalties
Core Concepts
Scope — What is a Product with Digital Elements (PDE)?
A 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:
- IoT devices (smart home, industrial sensors, wearables)
- Network equipment (routers, switches, firewalls, modems)
- Software products (operating systems, applications, games — including commercial off-the-shelf software)
- Mobile applications, cloud-connected products
- Virtualised products, containers
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.
Product Classification
| Class | Description | Examples | Conformity Route | |---|---|---|---| | Default | All PDEs not in Class I or II | Generic IoT devices, general software, games, simple smart devices | Self-assessment (Module A) | | Class I (Annex III) | Higher-risk products — 35 categories | Identity management software, password managers, browsers, VPNs, network monitoring tools, microcontrollers, routers for home use, smart meters, industrial automation controllers | Self-assessment OR third-party (manufacturer's choice) | | Class II (Annex IV) | Highest-risk products — 12 categories | Hypervisors, TPMs, industrial firewalls, industrial ICS/SCADA, hardware security modules (HSMs), smart card readers, industrial robots | Mandatory third-party (Notified Body) |
Roles and Responsibilities
| Role | Definition | Key Obligations | |---|---|---| | Manufacturer | Designs, develops, produces, or has PDEs designed/developed/produced under their name | All Annex I requirements; vulnerability handling; incident reporting; DoC; CE marking; 10-year record-keeping | | Authorised Representative | EU-based entity acting for a non-EU manufacturer | Holds DoC and technical documentation for authorities | | Importer | Brings PDEs from outside the EU into the EU market | Verify manufacturer compliance; affix own name/address; notify authorities of risk; 10-year records | | Distributor | Makes PDEs available on EU market other than manufacturer/importer | Verify CE marking and DoC; not knowingly distribute non-compliant products | | Open-Source Software Steward | Entity that supports open-source software placed on the market commercially | Light-touch obligations; cybersecurity policy; cooperation with authorities |
Skill Workflows
Workflow 1 — Product Classification and Scope Assessment
When to use: Determining whether a product is in scope and which class it falls into.
Steps:
- Identify whether the product has at least one network interface (direct or indirect connectivity).
- Check exclusions (medical devices, aviation, automotive, military, etc.).
- Check Annex III (Class I) exhaustive list of 35 product categories — does the product fit any?
- Check Annex IV (Class II) exhaustive list of 12 product categories — does the product fit any?
- If neither Annex applies, the product is Default class.
- Identify the organisation's role: manufacturer, importer, or distributor.
- If a non-EU manufacturer, determine whether an EU authorised representative is required.
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
Workflow 2 — Annex I Essential Requirements Gap Analysis
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):
- No known exploitable vulnerabilities at time of placing on market
- Secure by default configuration — minimal attack surface, unnecessary functions disabled
- Protection against unauthorised access — appropriate authentication, access control
- Confidentiality — protection of data at rest and in transit (encryption)
- Integrity — protection against manipulation; signed software updates
- Minimal data processing — data minimisation and privacy by design
- Protection of availability — resilience against denial of service
- Limited negative impact on other devices/networks
- Exploit mitigation mechanisms
- Security-relevant information disclosed to users
Annex I — Part II: Vulnerability Handling (Manufacturers must):
- Identify and document vulnerabilities in products and components (including third-party)
- Address vulnerabilities without delay — free security updates
- Apply a vulnerability disclosure policy (VDP) — coordinated disclosure
- Publish a point of contact for vulnerability reporting
- Share information with CERT/CSIRT networks
- Provide a Software Bill of Materials (SBOM) on request — at minimum: top-level dependencies
- Maintain free-of-charge security updates for the support period
- Notify ENISA and national CSIRTs of actively exploited vulnerabilities within 24 hours (early warning), followed by a full report within 72 hours
- Notify users promptly of security issues and remediation measures
Steps for gap analysis:
- Map current product security controls against each Part I requirement.
- Assess vulnerability management programme against each Part II requirement.
- Confirm existence of VDP and public point of contact.
- Confirm SBOM capability (at minimum, top-level open-source components).
- Determine support period commitment.
- Identify gaps, assign risk ratings, and propose remediation timeline.
Workflow 3 — Conformity Assessment and CE Marking
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:
- Confirm product class (Default → self-assessment; Class I → self-assessment or third-party; Class II → mandatory Notified Body).
- Prepare technical documentation (TD) — required elements per Annex VII.
- Conduct conformity assessment against Annex I requirements.
- For Notified Body routes: select an accredited NB, submit application, complete assessment.
- Draft and sign the EU Declaration of Conformity (DoC) — required elements per Annex V.
- Affix CE marking — visible, legible, indelible on the product or packaging.
- Retain TD and DoC for 10 years after placing on market.
Technical Documentation (Annex VII) must include:
- General product description and intended use
- Design and development documentation (architecture diagrams, threat model)
- Security risk assessment
- Cybersecurity measures implemented
- Test reports and evidence of conformity
- SBOM (at minimum, top-level dependencies)
- Vulnerability handling policies and procedures
Workflow 4 — Vulnerability Handling Programme
When to use: Building or reviewing a vulnerability management and disclosure programme.
Programme elements:
- Internal vulnerability tracking — inventory of components and dependencies; process to identify new CVEs affecting products.
- Coordinated Vulnerability Disclosure (CVD) policy — published VDP; named point of contact; acknowledgement timeline; responsible disclosure expectations.
- Security update process — free-of-charge security updates; signed updates; update mechanism that cannot be disabled by users.
- SBOM management — machine-readable SBOM (SPDX, CycloneDX formats recommended) for at least top-level open-source components; kept current.
- Art. 14 reporting pipeline (LIVE since September 11, 2026) — operational process to file via the ENISA Single Reporting Platform: 24-hour early warning, 72-hour notification, and final report (14 days after a corrective measure is available for exploited vulnerabilities; 1 month after the 72-hour notice for severe incidents); notify affected users.
- Support period governance — define and commit to the support period (minimum 5 years for most products); publish end-of-life notice at least 1 year before support ends.
- Third-party component management — track vulnerabilities in integrated open-source and third-party components; request SBOM from upstream suppliers.
Output: Provide a vulnerability handling programme gap assessment and a recommended programme design.
Workflow 5 — Support Period and End-of-Life Obligations
When to use: Defining support commitments and planning product end-of-life.
Support period rules:
- Must be at least 5 years, or the expected product lifetime if shorter
- Manufacturers must clearly communicate the support period to users
- Security updates must be free-of-charge and delivered promptly throughout the support period
- Updates must not degrade product security or functionality
- At end of support: notify users at least 1 year in advance; if possible, provide a migration path or final cumulative security update
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.
Reporting Is LIVE — Art. 14 via the ENISA SRP (state in every reporting answer)
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).
| Stage | Exploited vulnerability | Severe incident (Art. 14(5): impact on abilit
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
