nex-eu-hardware-compliance-docs
Draft EU Hardware Compliance Documents
Hardware teams need structured compliance drafts without inventing missing product facts. This guide helps an assistant draft CE, RoHS, and REACH documents for qualified review.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "nex-eu-hardware-compliance-docs" from https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-eu-hardware-compliance-docs/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "nex-eu-hardware-compliance-docs". Draft a CE declaration for SmartHub X1 by NexGen Tech using confirmed LVD 2014/35/EU and EMC 2014/30/EU references.
Expected outcome:
- Draft CE Declaration of Conformity
- Product: SmartHub X1. Manufacturer: NexGen Tech.
- Supplied directives: LVD 2014/35/EU and EMC 2014/30/EU.
- Manufacturer address, applicable standards, signatory, place, and date: [PLACEHOLDER].
- Status: Draft requiring qualified review before signature or use.
Using "nex-eu-hardware-compliance-docs". Prepare RoHS and REACH drafts for SmartHub X1. Supplier substance evidence is not yet available.
Expected outcome:
- Draft RoHS Statement: SmartHub X1. References: 2011/65/EU as amended by 2015/863/EU.
- Supporting substance evidence and compliance conclusion: [PLACEHOLDER].
- Draft REACH SVHC Declaration: Article 33 communication under Regulation 1907/2006.
- Candidate List date, substance information, and communication details: [PLACEHOLDER].
- Status: Evidence required before any compliance assertion.
Security Audit
SafeAll three static findings are false positives: the URLs are attribution links, and the footer contains no system reconnaissance instructions. No evidence found of prompt injection, data exfiltration, or executable behavior in the supplied guide. Referenced package assets are absent, which limits functionality rather than establishing a security threat.
Risk Factors
๐ Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-eu-hardware-compliance-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-eu-hardware-compliance-docs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
nexaiguy. (2026). nex-eu-hardware-compliance-docs security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs/audits/1BibTeX citation
@techreport{nexaiguy-nexaiguy-nex-eu-hardware-compliance-docs-2026,
author = {nexaiguy},
title = {nex-eu-hardware-compliance-docs security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nex-eu-hardware-compliance-docs security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-nex-eu-hardware-compliance-docs/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-eu-hardware-compliance-docs:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare an initial documentation package
Organize supplied product facts into CE, RoHS, and REACH drafts for an initial compliance review.
Assemble supplier declarations
Draft RoHS and REACH supplier paperwork while identifying missing substance information.
Refresh manufacturer documentation
Update draft declarations after product or standards changes, retaining placeholders for details that still require verification.
Try These Prompts
Help me prepare EU compliance drafts for [product and model]. Ask for missing manufacturer, directive, standards, representative, and substance information before drafting.
Draft a CE Declaration of Conformity for [product], manufactured by [legal name]. Use only [confirmed directives] and [verified standards]. Mark unknowns [PLACEHOLDER].
Using [supplier evidence], draft separate RoHS and REACH SVHC statements for [product]. Identify missing substance data. Do not assert compliance without supporting evidence.
Review [existing drafts] against [updated product details] and [verified regulatory references]. Revise CE, RoHS, and REACH drafts. List unresolved facts for qualified review.
Best Practices
- Provide verified manufacturer, product, directive, standards, and substance details before requesting a final draft.
- Check regulatory references against current official EU sources and retain dated supporting evidence.
- Have a qualified compliance professional review every draft and resolve placeholders before signature or distribution.
Avoid
- Treating generated declarations as certification or proof of compliance.
- Guessing applicable directives, standards, or substance status to eliminate placeholders.
- Assuming the missing templates or regulatory reference file are included in this package.