hardware-compliance
An agent skill by Platanor, from Platanor/hardware-compliance-handbook. Tags: audit, compliance, documentation, legal, security.
What it does
Reference knowledge base on EU hardware/IoT cybersecurity law, maintained by Platanor Technologies — covering the Cyber Resilience Act (Regulation (EU) 2024/2847), the Radio Equipment Directive cybersecurity requirements (Directive 2014/53/EU, Delegated Regulation (EU) 2022/30 as amended, EN 18031), the NIS2 Directive (Directive (EU) 2022/2555), and the Cybersecurity Act / EUCC certification framework (Regulation (EU) 2019/881). Use this skill whenever the user asks anything about CRA compliance, essential cybersecurity requirements (Annex I), product risk classification (Default, Important Class I/II, Critical), CE marking for products with digital elements or radio equipment, vulnerability and incident reporting (CRA Article 14 or NIS2 Article 23), CRA/RED/NIS2 penalties and fines, deadlines and transition periods, manufacturer/importer/distributor obligations, whether NIS2 applies to a hardware manufacturer or its customers, EUCC/CSA certification and assurance levels, how these four regulations relate to each other or to GDPR/the AI Act, harmonised standards status (prEN 40000 series/M/606, EN 18031-1/-2/-3), or general questions like "does the CRA apply to my product," "are we a NIS2 essential or important entity," "what's the difference between CRA and RED," "is EUCC certification mandatory," or "what happens if I don't comply." Also use this skill to fact-check claims about any of these four regulations, cite exact article text, or draft related content that needs to be accurate.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add Platanor/hardware-compliance-handbook --skill hardware-complianceOr copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/Platanor/hardware-compliance-handbook
cp -r hardware-compliance-handbook ~/.claude/skills/hardware-complianceSafety box score
Grade A, minimal risk: 7 of 100 risk points, rated 2026-09-23. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This is a documentation-only knowledge base about EU hardware/IoT cybersecurity law; it does not ship code, installers, or automation. The main risk is informational completeness: several important standards/scheme details are intentionally deferred to external live sources, so answers need cross-checking before relying on them for compliance decisions.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | The repo is Markdown knowledge content only; no scripts, shell commands, or code evaluators are shipped. |
| Network access | 1 (low) | It points the agent to live external sources such as EUR-Lex, ENISA, GitHub, and product databases for current text and status, but contains no downloader or outbound automation. |
| Filesystem reach | 0 (none) | There are no commands or instructions to write, delete, or modify files outside the working repo. |
| Secrets & credentials | 0 (none) | Nothing in the skill reads, requests, or manipulates tokens, keys, passwords, `.env` files, or browser sessions. |
| Privilege & persistence | 0 (none) | The skill does not require sudo, global installs, services, shell startup edits, or other privilege changes. |
| Instruction hijack surface | 0 (none) | It contains normal source-selection guidance and caveats, but nothing that tells the agent to ignore higher-priority instructions, skip confirmations, hide things, or follow untrusted remote instructions. |
| Irreversible actions | 0 (none) | The skill is advisory only; it does not post, deploy, pay, book, delete, or otherwise act on the user's behalf. |
| Transparency | 1 (low) | Some core legal details are intentionally left outside the repo, notably the EUCC implementing act and the EN 18031 standard texts, so not every claim can be fully audited from the shipped files alone. |
Before installing
- Check whether you need live access to EUR-Lex/ENISA, especially for the missing EUCC implementing act and EN 18031 text.
- Read `csa/eucc-certification.md` and `primary-sources/index.md` to see which claims are summary-only versus backed by mirrored primary text.
- Use it only as a reference source; verify any compliance conclusion against the current official text before relying on it.
Rated 2026-09-23 by an automated review of 28 files from the skill's repository.
Source
- Repository
- Platanor/hardware-compliance-handbook (all skills from this repository)
- Path
- SKILL.md
- Branch
- main
- Updated
- 2026-09-23
Related skills
- X Money guide — Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability.
- github-sensitive-data-cleanup — Scan and remove sensitive data (secrets, API keys, private domains/IPs, PII) from GitHub repository history.
- marketplace-health-check — Run a full 6-dimension health check of this Claude Code skills marketplace repo — code/script safety, documentation/SSOT consistency, security/PII leaks.
- security-reviewer — Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance.
- setting-up-cloudtrail-multi-region — Enables a multi-region AWS CloudTrail trail with S3 log storage, CloudWatch Logs integration.
- audit-prep-assistant — Prepares codebases for security review using Trail of Bits' checklist.