qte77/checking-compliance
plugins/embedded-dev/skills/checking-compliance/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-utils-plugin checking-complianceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 4:30 AM65.8s3 files scanned
SKILL.md
- name:
- checking-compliance
- description:
- 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.
- compatibility:
- Designed for Claude Code
- allowed-tools:
- Read, Write, WebSearch, WebFetch
- argument-hint:
- [device-description]
- stability:
- stable
- content-hash:
- sha256:70309f2eb68a0ceeef78777b3d23182c63a63ac3a4828b5278c407df0158ff83
- last-verified-cc-version:
- 1.0.34
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 scopereferences/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.mdwith:- Each applicable directive/standard
- Specific clauses relevant to the device type
- Test requirements (pre-compliance and certification)
- Generate requirements file at
docs/requirements.mdwith 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
Related Skills
qte77/triaging-security-report
development
VerifiedTrustedCommunity
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
2SKILL.mdUpdated Jul 18, 2026
qte77/auditing-website-seo-geo
development
VerifiedTrustedCommunity
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
1SKILL.mdUpdated Jun 14, 2026
qte77/researching-website-design
development
VerifiedTrustedCommunity
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-website-usability
development
VerifiedTrustedCommunity
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
1SKILL.mdUpdated Apr 19, 2026