CtrlK
BlogDocsLog inGet started
Tessl Logo

customs-trade-compliance

Codified expertise for customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance across multiple jurisdictions.

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/customs-trade-compliance/SKILL.md

The canonical home for this skill is customs-trade-compliance in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable codification of specialized trade-compliance expertise with clear sequenced workflows and properly signaled one-level-deep references. Its main weakness is conciseness: a long role preamble, conceptual intros, and narrative communication examples add length that could be trimmed without losing actionable value.

Suggestions

Trim the Role and Context preamble and the conceptual Incoterms introduction to the specialized compliance implications Claude would not already know.

Compress the narrative tone-calibration dialogues into compact template cues rather than full quoted example exchanges.

Consider moving the Regional Specialties and detailed penalty-framework breakdowns into a reference file so the body reads as a leaner overview pointing to depth.

DimensionReasoningScore

Conciseness

Most of the dense material (GRI rules, 19 USC § 1592 tiers, ISF 10+2 elements) is genuinely specialized and earns its tokens, but the role preamble, conceptual Incoterms intro, and the narrative tone-calibration dialogues are explanation that could be tightened, matching the 3-anchor "mostly efficient but includes some unnecessary explanation".

3 / 5

Actionability

Provides highly concrete, specific guidance — numbered decision frameworks, RVC formulas, citation-specific penalty multipliers, an 85% screening threshold, and timeline-bound escalation triggers — with only minor gaps where full detail is deferred to the reference files, fitting the 4-anchor "mostly executable guidance with minor gaps".

4 / 5

Workflow Clarity

Multiple workflows (classification, FTA qualification, valuation method hierarchy, screening hit assessment) are clearly numbered and sequenced with branching decision points and "document the rationale" steps, but they lack explicit validate→fix→retry feedback loops, sitting at the 4-anchor rather than 5.

4 / 5

Progressive Disclosure

Three real one-level-deep references (decision-frameworks.md, edge-cases.md, communication-templates.md) are well-signaled inline and consolidated in an Additional Resources section, but the 28KB body inlines substantial core-knowledge and regional detail beyond a lean overview, matching the 4-anchor "good structure, references mostly clear, minor organization gaps".

4 / 5

Total

15

/

20

Passed

Description

70%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.

The description is specific and occupies a well-distinguished niche with good domain keyword coverage, but it lacks an explicit "when to use" trigger clause, which caps its completeness at the midpoint. It reads as a capability inventory rather than a verb-action list with invocation guidance.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when classifying goods under HS/HTS/TARIC codes, selecting Incoterms, preparing import/export documentation, or screening restricted parties."

Reframe the capability nouns as concrete actions (e.g. "Classifies goods under HS codes, optimises duty via FTAs, screens restricted parties") to lift specificity toward the top anchor.

Include user-natural synonyms and file/term variants ("HS codes", "Incoterms", "FTAs", "import/export", "customs broker") to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Lists five concrete capability areas ("customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance") with multi-jurisdiction coverage, but frames them as expertise nouns rather than the verb-led actions of the 5-anchor example, so it sits just below the top anchor.

4 / 5

Completeness

Provides a clear "what" (codified expertise across five compliance areas and multiple jurisdictions) but has no "Use when..." clause or explicit trigger guidance, which the rubric caps at 3 — matching the 3-anchor example of a clear "what" with "when" missing.

3 / 5

Trigger Term Quality

Contains natural domain terms a trade-compliance user would say ("customs documentation", "tariff classification", "duty optimisation", "restricted party screening", "regulatory compliance"), but omits common variants users actually invoke such as "HS codes", "Incoterms", "FTAs", and "import/export".

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (customs/trade compliance with screening, classification, and duty optimisation) whose triggers are distinct and unlikely to fire for unrelated skills, matching the 5-anchor "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.