CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-eudr-due-diligence

Builds a complete EUDR due diligence file, applicability decision, DDS structure, geolocation checklist, and risk assessment, from your product list. Use when: Determine EUDR scope, company role, and compliance deadlines; Map products to Annex I CN codes including 2025 amendments; Generate geolocation data collection checklists for suppliers.

Quality

65%

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 ./plugins/nex-compliance/skills/nex-eudr-due-diligence/SKILL.md

The canonical home for this skill is nex-eudr-due-diligence in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

25%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 is a well-written marketing overview of the skill, but as a SKILL.md it fails at its primary job: it tells Claude what the skill would do without giving it any executable content — no decision tree, mapping tables, templates, or step sequence — and the referenced scripts and templates are explicitly not shipped. It reads like a landing page, not an operational skill.

Suggestions

Replace the descriptive bullets with the actual instructions: the applicability decision tree, the Annex I CN-code mapping table, the DDS field structure, the geolocation checklist fields, and the Article 10 / benchmark risk-assessment procedure.

Ship the referenced materials as bundle files (e.g., references/cn-codes.md, references/benchmarks.md, templates/dds.md) and link to them explicitly from the body so the overview points to real, one-level-deep content.

Cut the "Why use this", "Use cases", "Questions", and promotional footer sections, and move the compliance dates and 2025 amendment details into a clearly labeled section so time-sensitive facts don't bloat the core guidance.

DimensionReasoningScore

Conciseness

Large portions are promotional restatement rather than instruction: "EUDR hits anyone trading cattle, cocoa, coffee... and the December 2026 deadline is fixed", the "Use cases" section, the FAQ-style "Questions" section, and the footer plug for a paid catalog all repeat the description. It also embeds time-sensitive dates (30 December 2026, 30 June 2027, the December 2025 amendment, Implementing Regulation 2025/1093) outside any deprecated/old-patterns section, which the guidelines penalize. This matches the level-2 "noticeably verbose; several unnecessary explanations or padded sections" anchor better than level 3, since the padding is structural rather than incidental.

2 / 5

Actionability

The body only describes capabilities — "Runs the applicability decision tree", "Maps each product to Annex I by CN code", "Builds a country-benchmark-based risk assessment" — without any decision tree content, CN mapping table, checklist fields, DDS template, or concrete steps. It does supply high-level hints (specific regulation numbers, named artifacts, a sample result block), matching the level-2 anchor ("minimal concrete guidance; high-level hints but missing the specific steps to execute") rather than level 1, which would have no such specifics.

2 / 5

Workflow Clarity

The five "What it does" bullets imply a rough order (applicability → CN mapping → DDS structure → geolocation checklist → risk assessment) but no numbered sequence, no inputs/outputs per step, and no validation checkpoints (e.g., verifying benchmark levels or CN codes against current official lists is mentioned only as a caveat in "Known limitations", not as a step). This fits the level-2 anchor "rough sequence present but many gaps; steps poorly defined; validation absent"; level 3 would require explicitly listed steps.

2 / 5

Progressive Disclosure

No bundle files exist in this skill (references/, scripts/, assets/ are absent), and the body openly states "Scripts, extension source, and templates from the original package are not in this folder" — so the detailed materials the overview points to are unavailable rather than organized one level deep. The section headers are clean, but the content that clearly belongs in separate files (CN code tables, decision tree, checklist and DDS templates) is neither inlined nor present, matching the level-2 anchor for a minimal-structure stub rather than the level-3 anchor, which requires usable references.

2 / 5

Total

8

/

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.

A strong, domain-specific description that names concrete deliverables and includes an explicit, multi-trigger "Use when" clause. Its only flaws are a second-person slip ("your product list") and a few missing natural synonyms for the regulation's name.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and artifacts — "Builds a complete EUDR due diligence file, applicability decision, DDS structure, geolocation checklist, and risk assessment" — which is comprehensive for the domain. However, it slips into second person ("from your product list"), which the guidelines penalize by one point; without that it would match the level-5 anchor.

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Builds a complete EUDR due diligence file, applicability decision, DDS structure, geolocation checklist, and risk assessment") and an explicit "Use when:" clause with three concrete triggers (determine scope/role/deadlines, map CN codes, generate geolocation checklists). This matches the level-5 anchor; the level-4 anchor applies only when the "when" is less explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "EUDR", "due diligence", "compliance deadlines", "Annex I CN codes", "geolocation", "suppliers" — terms a compliance user would actually say. Common synonyms like "EU Deforestation Regulation" spelled out, "deforestation-free", or "TRACES" are missing, so it falls just short of the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"EUDR due diligence", "Annex I CN codes", and "geolocation data collection checklists" define a clear niche with distinct triggers; no other skill category would plausibly fire on these phrases. It cleanly matches the level-5 clear-niche anchor, not the level-4 minor-overlap anchor.

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

plugins/nex-compliance/skills/nex-eudr-due-diligence/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.