# 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

```bash
npx skillstore add nexaiguy/nex-eu-hardware-compliance-docs
```

## Metadata

- Status: approved
- Slug: nexaiguy-nex-eu-hardware-compliance-docs
- Version: 1.0
- Author version: 1.0
- Skillstore revision: r1
- Version status: invalid
- Tree hash: a7cc6e5e855d88142035e30f8a0b17a2b1ffe51509c529b7845838861c1037f5
- Author: nexaiguy
- GitHub username: nexaiguy
- License: MIT
- Repository: https://github.com/nexaiguy/nex-ai-skills/tree/463aaff26593654193deb52f24d18e80ec21e323/skills/nex-eu-hardware-compliance-docs
- Ref: 3ddfdca559084abffbfdd188f2ba14b597dcfd9c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/nexaiguy-nex-eu-hardware-compliance-docs
- Manifest: https://skillstore.pages.dev/api/skills/nexaiguy-nex-eu-hardware-compliance-docs/manifest

## Capabilities

- Guides collection of product, manufacturer, authorized representative, directive, standards, and restricted substance details.
- Guides drafting of CE Declaration of Conformity fields using supplied product information.
- Guides drafting of RoHS statements referencing Directive 2011/65/EU and amendment 2015/863/EU.
- Guides drafting of REACH SVHC declarations addressing Article 33 supplier communication.
- Directs the assistant to mark missing information as \[PLACEHOLDER\] instead of guessing.

## Use Cases

- 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.

## Prompt Templates

### Start a compliance intake

```
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

```
Draft a CE Declaration of Conformity for [product], manufactured by [legal name]. Use only [confirmed directives] and [verified standards]. Mark unknowns [PLACEHOLDER].
```

### Prepare substance declarations

```
Using [supplier evidence], draft separate RoHS and REACH SVHC statements for [product]. Identify missing substance data. Do not assert compliance without supporting evidence.
```

### Refresh a documentation package

```
Review [existing drafts] against [updated product details] and [verified regulatory references]. Revise CE, RoHS, and REACH drafts. List unresolved facts for qualified review.
```

## Limitations

- The package contains only a public guide; original scripts, extension source, and template assets are not included.
- The mentioned date-stamped regulatory reference file is absent, so current regulatory references require independent verification.
- Drafts do not establish compliance, replace testing, or provide legal verification.
- The guide does not cover machinery, medical device, or radio equipment specifics.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-11-02T12:41:06.197\+00:00
- Summary: All 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.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0