Platanor

Hardware Compliance Handbook — Security skill for Claude Code

Security community

AI-ready knowledge base of security & compliance regulations for hardware and connected-device manufacturers - structured, indexed, and machine-readable for LLMs and agents.

How to install Hardware Compliance Handbook

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Platanor/hardware-compliance-handbook and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hardware Compliance Handbook does

AI-ready knowledge base of security & compliance regulations for hardware and connected-device manufacturers - structured, indexed, and machine-readable for LLMs and agents.

Alternatives in Security

Maestro Knowledge — Intent-driven knowledge-store and Run knowledge lifecycle management — audit/prune, stage candidates (with sig 530 ★
Query Token Audit — Audit token security to detect scams, honeypots, and malicious contracts across BSC, Base, Solana, and Ethereu 483 ★
Bountyforge — All-round bug bounty skill for Claude Code parallelized agents for smart contract audits (EVM, Move, Solana, T 399 ★

README

Hardware Compliance Knowledge Base

**A fact-checked, open reference on the EU laws that govern hardware and IoT cybersecurity — CRA, RED, NIS2, and the Cybersecurity Act/EUCC, in one place instead of four.**

[![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/) [![Regulations covered](https://img.shields.io/badge/regulations-CRA%20%7C%20RED%20%7C%20NIS2%20%7C%20CSA%2FEUCC-blue)](#repository-structure) [![Maintained by](https://img.shields.io/badge/maintained%20by-Platanor%20Technologies-2f855a)](https://platanor.com)

Prepared by **Platanor Technologies** ([platanor.com](https://platanor.com)) — an embedded security firm for IoT device manufacturers.

**Contents:** [Quick start](#quick-start) · [What this is](#what-this-is) · [Repository structure](#repository-structure) · [Technical reference](#technical-reference-technical) · [Methodology](#methodology-and-sourcing) · [Using with an LLM](#how-to-use-this-with-an-llm) · [Claude Skill](#installing-this-as-a-claude-skill) · [Feedback](#feedback) · [License](#license) · [Discussions](https://github.com/Platanor/hardware-compliance-handbook/discussions)

Quick start

Just want an answer? Open `cra/faq.md`, `red/faq.md`, `nis2/faq.md`, or `csa/faq.md` — each is a practical Q&A for hardware/IoT manufacturers, no legal background required.
Working with an LLM? Drop a processed guide into your prompt and ask, e.g.: "Using cra/product-risk-classes.md and red/essential-requirements.md, does a Wi-Fi-connected baby monitor need a notified body, or can we self-assess?"
Need the exact legal wording? Every processed guide links back to its source in `primary-sources/` — full official text, chunked by article.
Need the engineering, not just the regulation? `technical/` covers how to actually build the thing the law asks