agentleFS
NexaiGuyNexaiGuy/nex-ai-skills/skills/nex-eudr-due-diligence/SKILL.md

nex-eudr-due-diligence

Skill1 starsChanged 16 days agoMITView on GitHub

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.

The file

Files
SKILL.md

Nex EUDR Due Diligence

Free skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.

What it does

  • Runs the applicability decision tree for Regulation 2023/1115: in or out of scope, role (operator, downstream operator, trader), size class, and applicable date (30 December 2026 or 30 June 2027).
  • Maps each product to Annex I by CN code, including the December 2025 amendment that removed certain printed products from scope.
  • Produces the Due Diligence Statement structure mirroring Annex II, ready for the EU Information System (TRACES).
  • Generates the geolocation data collection checklist with coordinate format rules and legality evidence per plot.
  • Builds a country-benchmark-based risk assessment (Implementing Regulation 2025/1093 plus the Article 10 criteria) with a negligible or non-negligible conclusion per supply chain.

Why use this

EUDR hits anyone trading cattle, cocoa, coffee, palm oil, rubber, soya, wood, or derived products on the EU market, and the December 2026 deadline is fixed. This skill takes a company from does this apply to me to a documented due diligence file, including the simplified routes for low-risk sourcing and the post-2025 reliefs for downstream companies that most summaries miss.

Use cases

  • An importer of coffee, cocoa, palm oil, soy, rubber, or timber preparing for the December 2026 deadline
  • A chocolate maker or furniture producer checking whether the downstream reliefs apply
  • Building the supplier geolocation data request and evidence file
  • A documented risk assessment per supply chain, with the low-risk simplified route where allowed

Known limitations

Output is a structured draft, not legal advice. The skill appends a disclaimer and the file needs professional review. Country benchmark levels and CN code mappings must be verified against the current official lists at the time of use. It structures the DDS but does not submit it to TRACES for you.

Example

Request

We import coffee from Brazil for the EU market. Are we in scope for EUDR, and what due diligence do we need to prepare?

Result

EUDR Applicability: In Scope

  • Role: Operator (Importer)
  • Deadline: 30 Dec 2026
  • Action: Full Due Diligence required.
  • Files Generated: Geolocation Checklist, Risk Assessment Template (Standard Risk: Brazil), and Annex II DDS Structure.

Questions

How does it handle product scope?

The skill maps products to Annex I by CN code and includes the December 2025 amendment which removed specific printed goods like books and newspapers.

Does it help with supplier data collection?

Yes. It generates a geolocation data checklist with coordinate format rules and legality evidence requirements per plot of land.

What risk assessment criteria are used?

It uses Implementing Regulation 2025/1093 country benchmarks and Article 10 criteria to conclude if risk is negligible or non-negligible.

Does it submit files directly to TRACES?

No. It drafts the structure and content required for the DDS, but the user must manually submit this data to the TRACES system.


Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.