Ear logo

Ear

Community
Sushegaad
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.

Overview

PublisherSushegaad
RepositoryClaude-Skills-Governance-Risk-and-Compliance
Skill nameear
Stars
950
Forks
184
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Sushegaad on GitHub. Read the source before you install it.

Installation

Install the Ear AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/ear/skills/ear
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git /tmp/Claude-Skills-Governance-Risk-and-Compliance
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills-Governance-Risk-and-Compliance/plugins/ear/skills/ear .claude/skills/ear
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ear in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ear on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ear is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Export Administration Regulations (EAR) Compliance Skill

Last verified: 2026-09-05

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

Regulatory Status — September 2026 (state where relevant)

Drone/UAV classification changed (final rule, 91 FR 52501, effective August 13, 2026) — apply this decision logic to every UAV question:

  1. Endurance < 3 hours → 9A012.a.1, controlled AT-only (NS2 removed): license-free to most destinations. Software/technology follows: NS removed from 9D001, 9D002, 9D004, 9E001 for sub-3-hour UAVs.
  2. Endurance ≥ 3 hours → 9A012.a.2: NS Column 1 + AT1, plus MT1 if range ≥ 300 km.
  3. Any endurance stays NS1/AT1 if the UAV incorporates controlled 6A003 thermal imagers, 6A005 lasers, or 7A001–7A005 navigation equipment.
  4. Military "specially designed" UAVs not described on the USML now classify in 9A610.a (BIS reversed its 2013 position); less-sensitive parts go to new 9A610.y.33; STA to Country Group A:5 available where the UAV cannot deliver ≥500 kg to ≥300 km.
  5. Military end-use/end-user controls (§744.21) now cover ECCNs 9A012, 9D001, 9D002, 9D004, 9E001 — screen destinations accordingly. The old wind-gust parameter is gone.

Enforcement signal (Aug 2026): BIS settled with Plexon, Inc. — $1.7M fully suspended (5 years, waived on external audit + clean record) for 8 unlicensed exports (~$179K) of neural-recording systems to China's Academy of Military Medical Sciences (Entity-Listed 2021). Lesson: research/medical technology is not exempt from Entity List screening.

AI-chip "diffusion" framework: the Jan 2025 IFR was never formally rescinded in the Federal Register; BIS announced non-enforcement (May 2025) and GAO (B-337935) held that announcement itself a CRA rule not submitted to Congress. Successor policy is country-specific rulemaking (e.g., the UAE rule, 91 FR 43034). Do not advise as if a replacement diffusion framework exists.


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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ear AI skill do?

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, vo...

Why use Ear on TypingMind?

Because you install it once and use it with any model. Ear is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ear in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/ear/skills/ear. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ear?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ear?

As many as you like. As long as a model supports skills, you can use Ear with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ear AI skill free?

Yes. It is published on GitHub by Sushegaad under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇