ワンクリックでManusで任意のスキルを実行

customs-adcvd-tariff-exposure

スター3

フォーク0

更新日2026年7月17日 16:02

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

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

deciqAI

deciqAI/knowledge-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Customs — AD/CVD & Tariff Exposure Cascade

Industry front door for second-order-thinking. 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 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.

Part of deciqAI Knowledge Skills — 228 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

このリポジトリの他の Skills

同じリポジトリ

10-10-10

deciqAI/knowledge-skills

Activate when: someone is making a decision under emotional pressure and worries they'll regret it later; someone says "I know I should do X but it feels too scary right now"; someone is about to quit, accept an offer, end a relationship, or have a hard conversation and is stuck; someone mentions "regret minimization," "what would future me say," or "Suzy Welch." Do NOT activate when: the decision has no medium- or long-term consequences (e.g., which lunch to order); the decision belongs to someone else and the user is being asked to ratify it. More: deciqai.com/s/10-10-10

2026-07-173

aarrr-pirate-metrics

deciqAI/knowledge-skills

Activate when: user says 'our growth is stalling and we don't know why,' 'product and marketing are arguing about whose fault it is,' 'where is our funnel breaking,' 'pirate metrics,' or 'acquisition vs activation vs retention.' Also activate for: designing end-to-end metrics for a new product, building a shared instrumentation framework across teams. Do NOT activate when: the product has no users yet (use lean-startup instead), or the bottleneck is already obvious and obvious to fix. More: deciqai.com/s/aarrr-pirate-metrics

2026-07-173

abductive-reasoning

deciqAI/knowledge-skills

Activate when: user says 'what's the most likely explanation,' 'why did this happen,' 'we think it's X but not sure,' 'we only have one theory,' 'the team has converged on an answer without checking alternatives,' or when diagnosing a bug/outage/symptom/anomaly under uncertainty. Do NOT activate when: the problem is purely deductive or mathematical (direct proof, not hypothesis); the situation allows direct observation or measurement that bypasses inference. More: deciqai.com/s/abductive-reasoning

2026-07-173

activation-onboarding-playbook

deciqAI/knowledge-skills

Activate when: signups don't turn into active/paying users; 'people sign up but don't stick', designing onboarding, improving activation; aha moment, time-to-value. Do NOT activate when: the problem is acquisition (no signups) or long-term retention of already-activated users (different lever). More: deciqai.com/s/activation-onboarding-playbook

2026-07-173

anchoring

deciqAI/knowledge-skills

Activate when: user says 'what's a fair price / starting number / ballpark'; counterparty just opened with a number; user is about to negotiate salary, valuation, or deal terms; user is making a forecast and a number has already been floated; user asks about 'first offer', 'framing effect', or 'being anchored'. Do NOT activate when: the number in question is a verifiable data point (audited financials, confirmed comparable) and is genuinely informative; or the decision is so trivial that the economic impact of anchoring is negligible. More: deciqai.com/s/anchoring

2026-07-173

ansoff-matrix

deciqAI/knowledge-skills

Activate when: user says 'where should we grow next', 'should we enter a new market', 'thinking about diversifying', 'new product vs new market', 'growth strategy', 'adjacent expansion', 'Ansoff', or is spreading resources across too many directions at once. Do NOT activate when: the firm has one clear unsaturated market (answer is always penetration — no matrix needed); or the question is about portfolio allocation across existing BUs (use BCG Matrix instead). More: deciqai.com/s/ansoff-matrix

2026-07-173

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. Adds domain triggers, example, packs only. Parent Process unchanged. Not legal advice. Scope is order-specific; consult AD/CVD scope rulings / counsel.

Why this variant

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

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.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/customs-adcvd-tariff-exposure.json