agentleFS
deciqAIdeciqAI/knowledge-skills/customs-origin-usmca-decision/SKILL.md

customs-origin-usmca-decision

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: determining country of origin; testing USMCA (or other FTA) preference eligibility; marking; 'does this qualify for duty-free?'; goods with multi-country inputs. Do NOT activate when: wholly-obtained single-country goods with no preference question. More: deciqai.com/s/customs-origin-usmca-decision

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If not by shift: is Regional Value Content (transaction-value or net-cost) met?

    line 21
  2. Distinctive:

    No supporting certification retained.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Customs — Country of Origin & USMCA Qualification

Industry front door for decision-tree. Adds domain triggers, example, packs only. Parent Process unchanged. Not legal advice. Origin is rule-specific; verify against the current USMCA text and CBP guidance.

Activate when: determining country of origin; testing USMCA (or other FTA) preference eligibility; marking; "does this qualify for duty-free?"; goods with multi-country inputs. Do NOT activate when: wholly-obtained single-country goods with no preference question.

Why this variant

The parent decision-tree maps branching qualification logic. Origin/preference is a decision tree: wholly obtained? → tariff-shift met? → RVC threshold met? → de minimis? Each branch leads to duty-free, MFN, or special treatment.

Domain inputs → parent's Process

Walk the branches:

  • Wholly obtained/produced entirely in territory? → originates.
  • Else: does each non-originating input meet the product-specific rule (tariff shift)?
  • If not by shift: is Regional Value Content (transaction-value or net-cost) met?
  • De minimis allowance for small non-originating value?
  • Confirm certification of origin support + marking rules (substantial transformation for marking).

Worked example

Assembly in Mexico using Chinese components. → Tree: check the PSR — do the Chinese inputs make the required tariff shift on assembly? If yes → USMCA-eligible with a valid certification; if no → test RVC/de minimis. Fails all → MFN duty + China Section 301 exposure. Document the path.

Compliance anchors

  • USMCA product-specific rules, RVC, de minimis; certification of origin recordkeeping; marking (19 CFR 134).

Packs

  • Solo broker: origin worksheet per product/BOM.
  • Brokerage: supplier solicitation for origin certs; PSR library.

Red flags

  • Claiming preference without the PSR/RVC actually met.
  • Confusing marking origin with preference origin.
  • No supporting certification retained.

Verification

  • Wholly-obtained vs PSR path determined
  • Tariff-shift / RVC / de minimis tested in order
  • Valid certification support on file
  • Marking origin assessed separately

Part of deciqAI Knowledge Skills. Core method: decision-tree.


Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/customs-origin-usmca-decision · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/customs-origin-usmca-decision.json

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.