How do I install the Checking Compliance skill?

Run npx skillmds@latest add qte77/checking-compliance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Checking Compliance safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Checking Compliance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Checking Compliance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Checking Compliance?

qte77 (@qte77) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Checking Compliance by qte77 — Agent Skill

Name: Checking Compliance
Author: qte77

Checking Compliance

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.

qte77 3a03524 3 files · 9.1 KB Updated Sep 17, 2026

File contents

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

---name: checking-compliancedescription: 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.---# Compliance Requirements Generation**Target**: $ARGUMENTSGenerate 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## Workflow1. **Parse device description** — Identify device type, markets (EU/US/both), wireless capability, power source, intended use2. **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)3. **WebSearch** for latest standard revisions if unsure about current edition4. **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)5. **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`)6. **Output next steps** — Explain how to break SYS-REQ into PRD-REQ and SW-REQ, then use `implementing-firmware`## Output Format### Compliance Checklist```markdown# 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```markdown# 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

Frequently asked questions