Activate when: goods may fall under an antidumping/countervailing duty order or Section 301; sourcing changes; 'are we exposed to AD/CVD or 301?'; scope ambiguity. Do NOT activate when: product clearly outside any order and no special tariff applies. More: deciqai.com/s/customs-adcvd-tariff-exposure
Scanned 9/3/2026
Install to Claude Code
npx -y skills add deciqAI/knowledge-skills --skill customs-adcvd-tariff-exposure --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Customs Adcvd Tariff Exposure?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/deciqai-customs-adcvd-tariff-exposure)More formats (shields.io, HTML) on the badges page.
---
name: customs-adcvd-tariff-exposure
description: "Activate when: goods may fall under an antidumping/countervailing duty order or Section 301; sourcing changes; 'are we exposed to AD/CVD or 301?'; scope ambiguity. Do NOT activate when: product clearly outside any order and no special tariff applies. More: deciqai.com/s/customs-adcvd-tariff-exposure"
---
# Customs — AD/CVD & Tariff Exposure Cascade
> **Industry front door for [second-order-thinking](../second-order-thinking/SKILL.md).** Adds domain triggers, example, packs only. Parent Process unchanged.
> **Not legal advice.** Scope is order-specific; consult AD/CVD scope rulings / counsel.
**Activate when:** goods may fall under an antidumping/countervailing duty order or Section 301; sourcing changes; "are we exposed to AD/CVD or 301?"; scope ambiguity.
**Do NOT activate when:** product clearly outside any order and no special tariff applies.
## Why this variant
The parent [second-order-thinking](../second-order-thinking/SKILL.md) traces downstream consequences others miss. AD/CVD and Section 301 exposure is a second-order trap: a classification or origin choice that looks fine at entry can, orders later, mean **retroactive duties, cash deposits, and importer liability** — the broker's reasonable-care exposure too.
## Domain inputs → parent's Process
- 1st order: stated HTS + origin → duty at entry.
- 2nd order: does the product fall within an **AD/CVD scope** (by description, not just HTS)? Section 301 China list?
- 3rd order: transshipment/evasion risk (EAPA), retroactive liquidation, importer's cash-deposit rate, successor liability.
- Parties: importer, surety, broker reasonable-care.
## Worked example
Steel component classified cleanly, origin "Malaysia," inputs from China.
→ Second-order: AD/CVD orders are scope-based; a Chinese-origin input transshipped through Malaysia can trigger evasion (EAPA) findings + retroactive duties. Verify substantial transformation and scope *before* entry; a binding scope ruling may be warranted.
## Compliance anchors
- AD/CVD orders + scope rulings (Commerce); Section 301 (USTR); EAPA (evasion); reasonable care.
## Packs
- **Solo broker:** AD/CVD + 301 screen per product/origin.
- **Brokerage:** scope-ruling trigger list; high-risk origin flags.
## Red flags
- Assuming HTS alone determines AD/CVD (it's scope-based).
- Origin claims that look like transshipment.
- No scope check on sourcing changes.
## Verification
- [ ] AD/CVD scope checked by product description, not just HTS
- [ ] Section 301 list exposure assessed
- [ ] Transshipment/evasion risk evaluated
- [ ] Scope ruling considered where ambiguous
---
Part of **deciqAI Knowledge Skills**. Core method: [second-order-thinking](../second-order-thinking/SKILL.md).
---
*Part of **deciqAI Knowledge Skills** — 237 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-adcvd-tariff-exposure** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*
*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/customs-adcvd-tariff-exposure.json*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!