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

91%

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

78%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, well-engineered knowledge skill: correctly sequenced decision workflows, exact regulatory citations and thresholds, current (dated) regulatory status, and a textbook progressive-disclosure bundle with three scoped, non-nested reference files. The main improvement levers are trimming inline tables that duplicate the references and adding one fully worked end-to-end classification example.

Suggestions

Trim or relocate the CCL Categories, Product Groups, and Parts Structure tables into references/ccl-eccn-guide.md, keeping only the ECCN format and a pointer inline — this reduces body↔reference duplication and token cost.

Add one worked end-to-end example (e.g., a hypothetical item traced from order-of-review through ECCN entry, Country Chart X-check, and exception analysis) to lift actionability from concrete guidance to fully executable.

Add an explicit re-validation loop for time-sensitive rules — e.g., a checkpoint to re-run ownership screening before the affiliates-rule stay lapses on January 10, 2027 — to close the workflow_clarity gap.

DimensionReasoningScore

Conciseness

The body is mostly efficient: dense tables carry the payload (Country Groups, RFC codes, restricted party lists), there is no 'what is the EAR' padding, and the regulatory-currency material is concentrated in a labeled "Regulatory Status — September 2026" section. It falls short of level 5 because some inline content could be trimmed or pushed to the references — the CCL Categories and Product Groups tables restate knowledge Claude largely has, and Steps 1–2 plus the Step 4 exception table noticeably duplicate content expanded in references/ccl-eccn-guide.md and references/license-exceptions.md.

4 / 5

Actionability

Concrete, executable guidance throughout: the mandatory four-step Order of Review, exact thresholds (25%/10% de minimis, 5-year recordkeeping, 50% affiliates ownership), the numbered UAV decision tree ("Endurance < 3 hours → 9A012.a.1... Endurance ≥ 3 hours → 9A012.a.2: NS Column 1 + AT1, plus MT1 if range ≥ 300 km"), a task→output-format table, and real portals/URLs (SNAP-R, trade.gov/consolidated-screening-list). It is below level 5 because there is no end-to-end worked example (one item walked from jurisdiction through Country Chart to exception) and Country Chart lookup is a pointer to the reference rather than an inline procedure; it is above level 3 because the guidance cites exact sections and decision logic, not vague direction.

4 / 5

Workflow Clarity

Steps 1–8 are explicitly numbered in the true compliance workflow order (jurisdiction → classification → license analysis → exceptions → end-user controls → special topics → licensing → recordkeeping), with embedded checkpoints such as "Critical: EAR99 is a classification, not a license exemption" and "Always screen all parties... before every transaction". It misses level 5 because there are no explicit feedback/re-validation loops (e.g., re-screen when ownership changes post-January 2027) and some checkpoints are advisory rather than procedural gates; it exceeds level 3 because the sequence is complete, correctly ordered, and punctuated with stop conditions (Red Flags, WMD end-uses).

4 / 5

Progressive Disclosure

The bundle structure is exemplary: three real, self-contained reference files verified on disk (references/license-exceptions.md, references/ccl-eccn-guide.md, references/compliance-program.md), each one level deep with no nested references. References are well-signaled twice — inline at point of need ("Reference file: references/license-exceptions.md for complete conditions") and in a dedicated Reference Files table describing each file's contents — matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

17

/

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 excellent description: it enumerates concrete capabilities comprehensively, uses third person, and closes with an explicit, specific 'Use for...' trigger clause. Two minor caveats keep it from being a flawless model: it claims "all license exceptions" while listing 13 symbols (GFT, which appears in the body, is omitted), and at ~150 words it is denser than the ideal concise example, though every clause names a real capability rather than fluff.

DimensionReasoningScore

Specificity

Quotes: "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... 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 lists many specific concrete actions spanning the entire compliance lifecycle (classification, licensing, screening, enforcement, program design), matching the 'comprehensive coverage' anchor. It exceeds the level-4 anchor because there are no minor gaps — every major EAR task type is named.

5 / 5

Completeness

Both halves are explicit: 'what' is the detailed capability enumeration, and 'when' is the concrete trigger clause "Use for any dual-use export control, CCL classification, or BIS compliance question". This clearly matches the level-5 anchor (explicit what AND when with concrete trigger phrases); it is above level 4 because the 'when' clause is specific rather than merely present.

5 / 5

Trigger Term Quality

The closing clause "Use for any dual-use export control, CCL classification, or BIS compliance question" supplies the natural user phrasings, and the body of the description includes the terms users would actually say: ECCN, EAR99, ITAR, Entity List, Denied Persons List, license exceptions, deemed export, de minimis. Coverage includes synonyms (dual-use / export control / BIS compliance / EAR vs ITAR), matching the comprehensive-synonyms anchor rather than the 'a few natural terms missing' level-4 anchor.

5 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — U.S. dual-use export controls under EAR/BIS — with distinct triggers (CCL, ECCN, BIS, EAR99, Entity List). The only adjacent skill type would be an ITAR/USML skill, and the description explicitly addresses that boundary ("jurisdiction analysis (EAR vs ITAR order of review)"), keeping conflict risk minimal.

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.