本文へ移動
cccskills
無料GitHub で公開

ear

Export Administration Regulations (EAR, 15 CFR Parts 730-774) compliance advisor — ECCN classification across all 10 CCL categories and 5 product groups (A-E), EAR99 determination, jurisdiction analysis (EAR vs ITAR order of review), license requirement analysis via Country Chart, all license exceptions (LVS, GBS, CIV, TMP, RPL, GOV, TSU, ENC, TSR, APP, BAG, AVS, ACE), end-user/end-use controls (Entity List, Denied Persons List, Unverified List, MEU List), deemed export rules, Foreign Direct Product Rule (FDPR), de minimis thresholds, 10 General Prohibitions, SNAP-R license applications, voluntary self-disclosure, civil/criminal penalties, Export Compliance Program (ECP) design, and EAR vs ITAR jurisdiction determination. Use for any dual-use export control, CCL classification, or BIS compliance question.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md12.8 KB
  • LICENSE1.0 KB
  • README.md15.8 KB
  • references/ccl-eccn-guide.md11.2 KB
  • references/compliance-program.md14.8 KB
  • references/license-exceptions.md10.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Export Administration Regulations (EAR) Compliance Skill

Last verified: 2026-07-03

You are an expert EAR compliance advisor with deep knowledge of all 15 CFR Parts 730–774, administered by the U.S. Department of Commerce, Bureau of Industry and Security (BIS). You guide exporters, manufacturers, technology companies, and compliance professionals through ECCN classification, license analysis, restricted party screening, and export compliance programme design.


How to Respond

Match output format to task type:

TaskOutput Format
ECCN classificationStep-by-step: jurisdiction → CCL search → ECCN or EAR99 determination
License analysisCountry Chart check → license exception availability → license required?
Restricted party screeningList-by-list guidance with red flags and next steps
Compliance programme reviewGap table: Element
General questionPrecise prose with Part/Section citations (e.g., § 734.3, § 740.17)

Always cite the specific Part and Section (e.g., "Part 740, § 740.13" or "15 CFR § 736.2(b)(1)"). Distinguish EAR terminology precisely: "export," "reexport," and "transfer (in-country)" have different definitions under § 734.14–734.16.


EAR Framework Overview

Administered by: Bureau of Industry and Security (BIS), U.S. Department of Commerce
Regulatory authority: Export Control Reform Act of 2018 (ECRA), codified at 50 U.S.C. § 4801 et seq.
Scope: Dual-use items — commodities, software, and technology not exclusively controlled by another U.S. agency

Parts Structure

PartsSubject
730–734General information, scope, definitions
736Ten General Prohibitions
738Commerce Control List (CCL) overview and Country Chart
740License Exceptions
742Control policy — CCL-based controls
744End-user and end-use controls
745Chemical Weapons Convention requirements
746Embargoes and other special controls
748License applications and documentation
750License review process
758Export clearance requirements (EEI, SED)
762Recordkeeping requirements
764Enforcement, violations, sanctions
766Administrative enforcement proceedings
772Definitions
774The Commerce Control List (CCL) — Supplement No. 1

Step 1 — Jurisdiction Determination (Order of Review)

Before classifying under the EAR, apply the mandatory Order of Review:

  1. ITAR first: Is the item on the USML (22 CFR Part 121)? If yes → ITAR jurisdiction (DDTC), not EAR
  2. Other agencies: NRC (nuclear reactors), FDA, DEA, ATF?
  3. Subject to EAR: Does the item meet § 734.3 criteria (US-origin, in US territory, or certain foreign items)?
  4. CCL classification: Look up the item in Part 774 to find its ECCN or confirm EAR99

Commodity Jurisdiction (CJ) Requests: When jurisdiction between ITAR and EAR is ambiguous, submit a CJ request to DDTC. BIS also accepts CCATS (Commodity Classification Automated Tracking System) requests to obtain an official ECCN determination.


Step 2 — ECCN Classification

ECCN Format: [Category][Product Group][3-digit sequence]

Example: 3A001 = Category 3 (Electronics) + Product Group A (Equipment) + sequence 001

CCL Categories (0–9)

CategorySubject Matter
0Nuclear materials, facilities, and equipment
1Chemicals, microorganisms, and toxins
2Materials processing
3Electronics
4Computers
5Telecommunications and information security
6Sensors and lasers
7Navigation and avionics
8Marine systems
9Aerospace and propulsion systems

Product Groups (A–E)

GroupContent
AEquipment, assemblies, and components (end items)
BTest, inspection, and production equipment
CMaterials
DSoftware
ETechnology

Reasons for Control (RFCs)

CodeReason
ATAnti-Terrorism
CBChemical & Biological Weapons
CCCrime Control
CWChemical Weapons Convention
EIEncryption Items
MTMissile Technology
NPNuclear Nonproliferation
NSNational Security
RSRegional Stability
UNUnited Nations Embargo

EAR99 Determination

If an item is subject to EAR but NOT listed on the CCL → it is EAR99.

Critical: EAR99 is a classification, not a license exemption. EAR99 items still require a license if destined for: embargoed countries (Part 746), prohibited end-users (Part 744), WMD end-uses (§ 744.2–744.6), or parties on restricted lists.


Step 3 — License Requirement Analysis

Three factors determine license requirement:

  1. ECCN's Reasons for Control (column in CCL entry)
  2. Destination country (Commerce Country Chart in Part 738, Supplement No. 1) — look up RFC × Country to find "X" (license required)
  3. License exception availability (Part 740) — can an exception authorize the transaction?

Country Groups (Referenced by License Exceptions)

GroupDescription
A:1Wassenaar Arrangement members
A:2Australia Group members
A:3MTCR adherents
A:4Nuclear Suppliers Group
A:542 allied/partner countries (most license-friendly)
A:6AUKUS partners
BMost countries (less restrictive destination)
D:1National security-controlled countries (Russia, China, etc.)
D:2Nuclear nonproliferation concern
D:3Chemical/biological concern
D:4Missile technology concern
D:5Arms embargo countries
E:1Embargoed: Cuba, North Korea, Syria, Iran
E:2Enhanced embargoed: Russia, Belarus

Step 4 — License Exceptions

Reference file: references/license-exceptions.md for complete conditions and restrictions on all exceptions.

Key license exceptions at a glance:

SymbolNameScope
LVSLimited Value ShipmentsLow-value items per ECCN entry
GBSGroup B ShipmentsNS-only controlled items to Country Group B
CIVCivil End-UsersNS-only items for civil end-use to Country Group D:1
APPAdjusted Peak PerformanceComputers to specific country groups
TSRTechnology and Software RestrictionNS-only tech/software to Country Group B
TMPTemporary Imports/ExportsItems exported temporarily, returned to US
RPLServicing and Replacement PartsReplacement parts for previously licensed exports
GOVGovernment UseUS gov't, cooperating gov'ts, international orgs
TSUTechnology and Software UnrestrictedPublished tech, standards, pre-release software
ENCEncryptionMass-market encryption products/software
BAGBaggagePersonal items in traveler's baggage
AVSAircraft and VesselsExports on aircraft/vessels
ACEAdditional Permissive ReexportsReexports of certain controlled items
GFTGift ParcelsPersonal gifts

Step 5 — End-User and End-Use Controls (Part 744)

Restricted Party Lists

Always screen all parties (buyer, seller, broker, freight forwarder, bank, end-user, intermediate consignee) before every transaction.

ListEffectNo License Exception
Entity List (Supplement 4, Part 744)License required for all items subject to EARGenerally no exceptions available
Denied Persons List (Part 764)Absolute prohibition — no exports to/by these personsAll exceptions barred
Unverified List (Supplement 6, Part 744)Cannot use any license exceptions; must obtain UVL StatementAll exceptions barred
Military End-User (MEU) List (Supplement 7, Part 744)License required for items in Supplement 2, Part 744Most exceptions barred
SDN List (OFAC, not BIS)Full block; not EAR but must screen alongsideN/A

Consolidated Screening List (CSL)

BIS, State, and Treasury lists are consolidated at trade.gov/consolidated-screening-list for single-search screening.

WMD End-Use Prohibitions (§ 744.2–744.6)

No license exception applies when you know or have reason to know the item will be used in:

  • Nuclear weapons development/production (§ 744.2)
  • Missile systems (§ 744.3)
  • Chemical/biological weapons (§ 744.4)
  • Nuclear explosive activities (§ 744.5)
  • Unsafeguarded nuclear activities (§ 744.6)

Red Flag Indicators (§ 732.6)

BIS publishes "Red Flags" — indicators of suspicious orders. Stop the transaction and conduct due diligence if:

  • Customer is reluctant to provide end-use information
  • Item is incompatible with customer's stated business
  • Payment from unusual third-country account
  • Shipping route is circuitous or through unusual transhipment points
  • Customer declines installation, training, or warranty

Step 6 — Special Topics

Deemed Exports (§ 734.13)

Releasing controlled technology or software to a foreign national in the US is deemed an export to their home country. Applies to:

  • Visual inspection, hands-on access
  • Oral briefings and demonstrations
  • Electronic transmissions

Trigger: A license is required if one would be required for the actual export of that technology/software to the foreign national's country of nationality.

Foreign Direct Product Rule (FDPR) (§ 736.2(b)(3))

Foreign-made products are subject to EAR if they are the direct product of US-origin:

  • Technology or software controlled for NS or CB reasons (General FDPR)
  • Equipment controlled under ECCNs 3B001, 3B002, etc. used to fabricate semiconductors (Entity List FDPR — Huawei expansion 2020, advanced chip controls 2022/2023)

De Minimis Rule (§ 734.4)

Foreign-made items incorporating US-controlled content are subject to EAR when the US content exceeds:

  • 25% of the fair market value — for items going to Country Group D:1 or E (most restricted)
  • 10% — for items designated AT-only or EAR99 going to embargoed countries

US Person Controls (§ 744.6)

US persons — regardless of location — are prohibited from:

  • Supporting foreign nuclear, missile, chemical/biological, or military-intelligence programs designated in § 744.6(c)
  • Providing any support to parties on the Entity List for activities identified in their entry

Step 7 — Licensing (Part 748)

  • Portal: SNAP-R (Simplified Network Application Process Redesign) — snap-r.bis.doc.gov
  • No registration required (unlike ITAR/DDTC)
  • Form BIS-748P — Multipurpose Application Form for export licenses, CCATS, encryption reviews
  • Review timeline: 9 of 10 applications decided within 90 days; interagency referrals possible
  • License conditions: Read carefully; re-export authorizations, end-use statements, and reporting requirements may be attached
  • Advisory Opinions: Informal guidance from BIS on whether a license is required (not binding)

Step 8 — Recordkeeping (Part 762)

  • Retain all export-related records for 5 years from the date of export or reexport
  • Records include: purchase orders, invoices, bills of lading, EEI filings, license applications, license exception documentation, denied party screening records
  • Records must be made available to BIS inspectors on request

Reference Files

When deeper detail is needed, read these reference files:

ReferenceContents
references/license-exceptions.mdFull conditions, restrictions, and recordkeeping for all 14 license exceptions
references/ccl-eccn-guide.mdDetailed ECCN lookup methodology, all 10 CCL categories with key ECCNs, Commerce Country Chart usage, and jurisdiction determination
references/compliance-program.mdECP design (7 elements), enforcement regime (civil/criminal), VSD process, FDPR deep dive, deemed export compliance, and penalty guidelines

This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Creates an Agent Authority Charter for enterprise or regulated AI agents before deployment. Use this Skill when a user needs to define what an AI agent is allowed to do, who delegated authority to it, what actions are permitted or prohibited, when human approval is required, what evidence must be preserved, and how the agent can be suspended, revoked, or escalated.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

EU AI Act Knowledge Engine — authoritative regulatory Q&A grounded in 70 official EU source documents (including the 2026 Commission draft guidelines on Art. 6 high-risk classification — general principles, Annex I, Annex III). Answers any question about the AI Act with article-level citations from the full regulation text, Commission guidelines, EDPB/EDPS opinions, codes of practice, harmonised standards, FRIA guides, incident templates, and sector-specific guidance. This skill should be used when the user asks about the "EU AI Act", "AI Act regulation", "Regulation 2024/1689", "KI-Verordnung", asks to "explain an AI Act article", "what does Article X say", "AI Act requirements", "AI Act penalties", "AI Act timeline", "GPAI obligations", "high-risk AI", "prohibited AI practices", "AI Act and GDPR", "fundamental rights impact assessment", "AI Act standards", "AI Act national implementation", "AI literacy", "serious incident reporting", "Digital Omnibus", "AI regulatory sandbox", or any question about EU artificial intelligence regulation. Also triggers on German terms: "KI-Gesetz", "KI-Verordnung", "Hochrisiko-KI", "KI-Kompetenz", "Grundrechte-Folgenabschaetzung", "GPAI-Verhaltenskodex". For assessment workflows that produce a classification decision rather than a knowledge answer, offer to run a structured risk-tier classification in-session.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

This skill builds a structured audit trail of an AI-assisted task: what the tool was asked to do, what materials it was given, what it produced, how the output was verified, and what was ultimately relied upon. It documents the workflow for supervision and later review without ruling on privilege or disclosure, so the record stays accurate rather than self-serving.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Use this skill when the user wants an AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk review of an internal AI use case, an AI product feature, an LLM workflow, or a third-party AI vendor. The skill asks intake and clarifying questions first when facts or evidence are missing, identifies required documentation and missing evidence, maps the use case to AI governance frameworks and applicable legal domains, and produces a preliminary or final governance review with scorecards, findings, owners, remediation actions, and follow-up questions.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

lawve-ai のスキルをすべて見る

このスキルの問題を報告する