CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

itar

Expert ITAR compliance advisor for US defense contractors, exporters, and manufacturers. Use this skill for any question about 22 CFR Parts 120-130, the United States Munitions List (USML), DDTC registration, export license applications (DSP-5/73/94), Technical Assistance Agreements (TAA), Manufacturing License Agreements (MLA), brokering regulations (Part 129), deemed export rules for foreign nationals, technology control plans, voluntary disclosures, violation mitigation, jurisdiction determination (ITAR vs EAR), or US Munitions List category scoping. Trigger even if the user doesn't say "skill" — any ITAR or US defense export control question should use this skill.

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.

The content is a well-structured, highly actionable regulatory playbook with excellent progressive disclosure — all three referenced bundle files are real, well-signaled, and one level deep. Its main weaknesses are token efficiency: it inlines reference-style and known-concept material (the Parts 120-130 table, deemed-export definition) and embeds extensive dated regulatory status that will age, and its workflows stop short of explicit error-recovery loops.

Suggestions

Move the Parts 120-130 regulatory-structure table and the deemed-export concept definition into references/ (keeping only the penalty figures and §126.1 list, which Claude cannot be trusted to recall), trimming roughly 30 lines of body content.

Relocate the dated 'Regulatory Status — November 2026' bullets and the August 2026 BAE enforcement benchmark into a dedicated dated reference file (e.g., references/regulatory-status.md), leaving one 'check current rule status' pointer plus the 'Last verified' stamp in the body.

Add explicit recovery checkpoints to the licensing and TAA/MLA workflows (e.g., what to do when DDTC returns an application unpaid/refused, or when agreement amendments are required mid-term), mirroring the fallback logic already present in the jurisdiction workflow.

DimensionReasoningScore

Conciseness

The body is mostly tabular and terse, but it re-explains concepts Claude already knows (the full Parts 120-130 structural table, "A deemed export occurs when ITAR-controlled technical data is released to a foreign national inside the US", the role preamble) and carries substantial time-sensitive specifics — fee tiers, the August 2026 BAE benchmark, and a nine-bullet "Regulatory Status — November 2026" section with FR citations and expiry dates — that are not placed in an old-patterns/deprecated section. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' better than 4, where over-explanation would be only minor; the consolidated, 'Last verified: 2026-11-06'-stamped regulatory-status section mitigates but does not remove the time-sensitivity penalty.

3 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: portal URLs (registration.pmddtc.state.gov, D-Trade, DECCS), form numbers (DS-2032, DSP-5/73/94, DV-1), exact fees and deadlines ($2,750 tier, 60-day renewal, 5-day change notice, 5-year retention), penalty figures with statutory citations, a clause-by-clause TAA/MLA requirement list, and a per-task output-format table. Specific guidance covers the common cases, matching the top anchor as adapted for instruction-only skills, where absence of code is not penalized.

5 / 5

Workflow Clarity

All eight workflows are clearly sequenced with numbered steps, and several include conditional branches and checkpoints (jurisdiction: USML test → specially designed test → EAR fallback → CJ flag; deemed exports: "Verify no ITAR license is required... If required: obtain TAA"; the standing rule "Always check the current 22 CFR § 126.1 list and OFAC sanctions before any transaction"). This fits 'Clear sequence with most checkpoints present; minor validation gaps' — it falls short of 5 because most workflows lack explicit feedback/recovery loops (e.g., what to do when a license application is returned or a CJ determination conflicts with the analysis).

4 / 5

Progressive Disclosure

The body is a genuine overview plus eight core workflow summaries, and every deep-dive is correctly pushed one level deep: the three referenced files (usml-categories.md, licensing-guide.md, compliance-program.md) all exist in references/, are signaled inline at the end of the relevant sections ("Reference USML categories → references/usml-categories.md") and consolidated in a "Reference Files — Load as needed" section with one-line descriptions. This matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

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.

This is an exemplary description: it states the audience and role, exhaustively enumerates the skill's topic coverage with specific regulatory vocabulary, and gives explicit, even emphatic, trigger guidance. Every dimension lands at the top anchor without verbosity or over-claiming.

DimensionReasoningScore

Specificity

The description enumerates thirteen concrete capability areas — "DDTC registration, export license applications (DSP-5/73/94), Technical Assistance Agreements (TAA), Manufacturing License Agreements (MLA), brokering regulations (Part 129), deemed export rules... technology control plans, voluntary disclosures, violation mitigation, jurisdiction determination (ITAR vs EAR)" — comprehensive coverage of the ITAR advisory domain with specific form numbers and regulatory scopes. It matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than 4, since no meaningful ITAR topic area is missing.

5 / 5

Completeness

Both halves are explicit: the 'what' is "Expert ITAR compliance advisor for US defense contractors, exporters, and manufacturers" with a full topic inventory, and the 'when' is stated twice — "Use this skill for any question about..." and "Trigger even if the user doesn't say 'skill' — any ITAR or US defense export control question should use this skill". This clearly matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; the anchor-4 case ('when' could be more explicit) does not apply.

5 / 5

Trigger Term Quality

It captures the natural terms a user with this need would say — "ITAR", "US Munitions List (USML)" (both acronym and full name), "DDTC registration", "deemed export", "Technical Assistance Agreements", "voluntary disclosures", "ITAR vs EAR", "US defense export control" — plus a broad catch-all ("any ITAR or US defense export control question"). This meets the anchor for comprehensive coverage including synonyms; the only neighboring anchor (4) applies when natural terms are noticeably missing, which is not the case here.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (US ITAR / 22 CFR 120-130 defense export control) with domain-specific triggers like DSP-5, TAA/MLA, and USML that no general or adjacent skill would claim; the deliberate inclusion of "jurisdiction determination (ITAR vs EAR)" is an explicit scope statement, not accidental overlap. This matches 'Clear niche with distinct triggers; minimal conflict risk'.

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/itar/skills/itar/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.