Checking compliance

Skill qte77/claude-code-plugins/plugins/embedded-dev/skills/checking-compliance

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install

npx -y skills add qte77/claude-code-plugins --skill checking-compliance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generates compliance requirements from CE/FCC/UL standards for a device description. Use when starting a new embedded product, checking regulatory compliance, or generating initial SYS-REQ entries from applicable directives.

SKILL.md

2.9 KB, as published. Nobody here has run it

Compliance Requirements Generation

Target: $ARGUMENTS

Generate a compliance checklist and initial requirements file from applicable regulatory standards based on the device description.

References (MUST READ)

Read these before proceeding:

references/compliance-standards.md — Applicable directives, standards, and their scope
references/requirement-hierarchy.md — SYS-REQ → PRD-REQ → SW-REQ ID conventions

Workflow

Parse device description — Identify device type, markets (EU/US/both), wireless capability, power source, intended use
Select applicable directives:
- EU: LVD (2014/35/EU) + EMC (2014/30/EU) + RED (2014/53/EU if wireless) + RoHS + REACH
- US: UL 62368-1 + FCC Part 15 (+ Part 18 if ISM)
WebSearch for latest standard revisions if unsure about current edition
Generate compliance checklist at docs/compliance-checklist.md with:
- Each applicable directive/standard
- Specific clauses relevant to the device type
- Test requirements (pre-compliance and certification)
Generate requirements file at docs/requirements.md with SYS-REQ entries:
- One SYS-REQ per applicable standard clause
- Include norm reference in each entry (e.g., SYS-REQ-001: EN 55032 Class B conducted emission limits)
Output next steps — Explain how to break SYS-REQ into PRD-REQ and SW-REQ, then use implementing-firmware

Output Format

Compliance Checklist

# Compliance Checklist: <Device Name>

## Markets: <EU / US / Both>

### EU Directives
- [ ] LVD 2014/35/EU — IEC 62368-1:2023
  - Clause 5.4: Electrically-caused fire
  - Clause 6.3: Electric shock
- [ ] EMC 2014/30/EU — EN 55032:2015+A1:2020
  ...

Requirements File

# Requirements: <Device Name>

## System Requirements (SYS-REQ)

| ID | Description | Norm Reference | Status |
|----|-------------|----------------|--------|
| SYS-REQ-001 | Device shall meet EN 55032 Class B conducted emission limits | EN 55032:2015+A1:2020 §5 | open |

Rules

Always include norm version numbers — never reference a standard without its edition
When in doubt about applicability, include the standard and note it as "to be confirmed"
Separate safety (LVD/UL) from EMC from environmental (RoHS/REACH) requirements
Do NOT generate PRD-REQ or SW-REQ — that is the user's refinement step