CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-eu-hardware-compliance-docs

Generates CE Declaration of Conformity, RoHS statement, and REACH SVHC declaration templates from your hardware product details. Use when: Create a draft CE Declaration of Conformity for new electronics; Generate RoHS 3 compliance statements for supplier files; Draft REACH SVHC declarations for Article 33 requirements.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-eu-hardware-compliance-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as a marketing/README page rather than operational skill instructions: it describes capabilities and disclaimers but ships no templates, document structures, or executable workflow, and admits the original package's scripts and templates are absent. Section organization is decent, but the claimed reference file is a dangling pointer and the content cannot actually drive the promised document generation.

Suggestions

Include the actual CE DoC, RoHS, and REACH template structures (or the referenced reference file with date-stamped directive data) in the bundle so the body's claims are backed by real files.

Replace the prose "Runs a structured intake" description with a numbered step sequence for the intake and document generation, including a checkpoint for marking unavailable values as [PLACEHOLDER].

Remove the promotional footer, "Why use this" section, and FAQ that restates the description to tighten token efficiency and keep the body focused on instructions.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but the "Why use this" section, a FAQ that largely restates the description, and the promotional footer ("More skills, including the paid catalog") are unnecessary content beyond the 'minor trims' of anchor 4.

3 / 5

Actionability

The body describes rather than instructs: it names intake fields ("manufacturer legal name, EU authorized representative, applicable directives, standards, restricted substances") but provides no templates, document structures, or commands, and explicitly states "Scripts, extension source, and templates from the original package are not in this folder" — only high-level hints with the specific steps to execute missing.

2 / 5

Workflow Clarity

"Runs a structured intake" is asserted but never sequenced into steps, and no validation checkpoints or error handling appear anywhere; a rough process shape (intake → templates → placeholders) exists with many gaps and no validation, matching anchor 2.

2 / 5

Progressive Disclosure

The body is short with well-organized sections, but the FAQ references "a reference file with date-stamped directive information" that does not exist in the bundle (no references/, scripts/, or assets/ directories), and the templates/scripts that clearly belong in separate files are simply absent rather than appropriately split, keeping it at 'some structure but could be better organized'.

3 / 5

Total

10

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete deliverables, includes an explicit 'Use when:' clause with three realistic trigger scenarios, and occupies a distinctive niche. The only flaws are a second-person possessive in the input description and a few missing natural synonyms like 'CE marking'.

DimensionReasoningScore

Specificity

"Generates CE Declaration of Conformity, RoHS statement, and REACH SVHC declaration templates from your hardware product details" names three concrete deliverables and covers the skill's full domain (anchor 5), but the second-person "your hardware product details" triggers the required 1-point specificity reduction.

4 / 5

Completeness

It explicitly answers both what ("Generates CE Declaration of Conformity, RoHS statement, and REACH SVHC declaration templates") and when ("Use when: Create a draft CE Declaration of Conformity for new electronics; Generate RoHS 3 compliance statements for supplier files; Draft REACH SVHC declarations for Article 33 requirements") with concrete trigger phrases, matching the anchor 5 example; anchor 4 would require a less explicit 'when' clause.

5 / 5

Trigger Term Quality

Terms like "CE Declaration of Conformity", "RoHS", "REACH SVHC", "Article 33", and "supplier files" are exactly what a user needing this skill would say, but common variations such as "CE marking" or "DoC" are missing, matching "good keyword coverage; a few natural terms missing".

4 / 5

Distinctiveness Conflict Risk

EU hardware compliance documentation (CE/RoHS/REACH) is a clear niche with highly distinctive regulatory trigger terms and minimal overlap with other skills; anchor 4's 'minor overlap risk with closely related skills' does not apply since no closely related generic trigger terms are used.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-eu-hardware-compliance-docs/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.