CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, professionally structured compliance skill: the eight-step workflow follows the real order of review, the September 2026 regulatory-status section supplies genuinely current knowledge Claude cannot reliably recall, and progressive disclosure is exemplary with three well-organized, one-level-deep reference files. The main cost is conciseness — several encyclopedic tables of standard regulatory reference data (CCL categories, product groups, RFC codes, country groups) are inlined in SKILL.md instead of living in the references, and actionability would rise further with a worked end-to-end example.

Suggestions

Move the encyclopedic tables Claude already knows — CCL Categories 0–9, Product Groups A–E, Reasons for Control codes, and the Parts structure table — into references/ccl-eccn-guide.md, keeping in SKILL.md only the entries that correct common misreadings (e.g., the E:1/E:2 and D:5 country groups).

Trim the 14-row license-exception glance table to the handful most often invoked (LVS, GBS, TSR, ENC, TMP) and rely on the existing pointer to references/license-exceptions.md, which already documents all exceptions in full.

Add one worked end-to-end example — e.g., classifying a sub-3-hour UAV with a 6A003 thermal imager through jurisdiction, ECCN, Country Chart, and exception analysis — to convert the remaining high-level directives into an executable pattern.

DimensionReasoningScore

Conciseness

Mostly efficient tabular presentation, but a substantial portion restates concepts Claude already knows — the CCL Categories 0–9 table, Product Groups A–E, Reasons for Control codes, the Parts structure table, Country Groups, and a 14-row license-exception glance table duplicating references/license-exceptions.md. This matches the anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 2 because there is no prose padding and the genuinely non-obvious content (2026 regulatory status, decision logic, thresholds) earns its tokens, and not 4 because the volume of already-known reference data inlined is more than minor.

3 / 5

Actionability

Concrete, directly executable guidance dominates: 'Endurance < 3 hours → 9A012.a.1, controlled AT-only', 'Three factors determine license requirement', '25% of the fair market value... 10% for AT-only or EAR99 going to embargoed countries', 'Retain all export-related records for 5 years', plus specific URLs (snap-r.bis.doc.gov, trade.gov/consolidated-screening-list) and section citations throughout. This matches 'Mostly executable guidance; concrete code or commands with minor gaps' — a few directives remain high-level ('Read license conditions carefully', 'Records must be made available to BIS inspectors on request'), so 5's 'specific examples cover the common cases' is not fully met (no end-to-end worked example).

4 / 5

Workflow Clarity

The Steps 1–8 sequence mirrors the real compliance order of review (jurisdiction → classification → license requirement → exceptions → end-user controls → licensing → recordkeeping) with genuine checkpoints: 'When jurisdiction between ITAR and EAR is ambiguous, submit a CJ request', 'Stop the transaction and conduct due diligence' on red flags, and the critical EAR99-not-a-license-exemption warning. This matches 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because some checkpoints are advisory rather than explicit gates (e.g., no explicit instruction to verify a provisional ECCN against the current e-CFR before finalizing), and not 3 since the sequence is coherent and checkpoints are mostly explicit.

4 / 5

Progressive Disclosure

The body is a genuine overview that defers detail to three real, verified, one-level-deep reference files, clearly signaled via a contents table ('Full conditions, restrictions, and recordkeeping for all 14 license exceptions', etc.) and an inline pointer at Step 4 ('Reference file: references/license-exceptions.md for complete conditions and restrictions on all exceptions'). Verified against the actual bundle: all three referenced paths exist and contain no nested references, matching the anchor 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: highly specific capability enumeration, an explicit 'Use for...' trigger clause in third person, comprehensive natural domain terminology, and a sharply defined niche with the EAR/ITAR boundary explicitly disambiguated. The only nitpick is length — enumerating every license exception acronym is borderline keyword-stuffing — but it is dense signal rather than fluff, so it does not violate any dimension anchor.

DimensionReasoningScore

Specificity

The description lists many specific concrete actions with comprehensive coverage — 'ECCN classification across all 10 CCL categories', 'EAR99 determination', 'jurisdiction analysis (EAR vs ITAR order of review)', 'license requirement analysis via Country Chart', 'deemed export rules', 'Foreign Direct Product Rule (FDPR), de minimis thresholds', 'SNAP-R license applications, voluntary self-disclosure, civil/criminal penalties, Export Compliance Program (ECP) design'. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; nothing is vague, so 4 ('minor gaps in coverage') is too low.

5 / 5

Completeness

Both questions are answered explicitly: the what is the extensive capability enumeration, and the when is the explicit trigger clause 'Use for any dual-use export control, CCL classification, or BIS compliance question'. This matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; 4 would apply only if the when-clause were weaker or less concrete.

5 / 5

Trigger Term Quality

Natural trigger terms are comprehensive for this domain: 'dual-use export control', 'CCL classification', 'BIS compliance' in the when-clause, plus ECCN, EAR99, ITAR, Entity List, de minimis, and 'export control' synonyms throughout. This matches the anchor 'Comprehensive coverage of natural terms including synonyms'; score 4 ('a few natural terms missing') would understate the coverage, as users of this skill phrase questions using exactly this jargon.

5 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (U.S. EAR/BIS dual-use export controls) and even self-distinguishes from the nearest competing skill territory with 'EAR vs ITAR order of review' and 'EAR vs ITAR jurisdiction determination'. Per the anchor 'Clear niche with distinct triggers; minimal conflict risk'; 4 ('minor overlap risk with closely related skills') fits worse since the ITAR boundary is explicitly drawn.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

Path

plugins/ear/skills/ear/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.