CtrlK
BlogDocsLog inGet started
Tessl Logo

customs-trade-compliance

Codified customs and trade compliance expertise — HS/HTS tariff classification with GRI rules, commercial invoices and entry documentation, Incoterms 2020, FTA qualification and duty optimization (USMCA, RCEP, FTZs, drawback), denied-party screening, and penalty mitigation across US, EU, UK, and APAC jurisdictions. Use when classifying goods, preparing import/export documentation, screening restricted parties, responding to customs audits or CF-28/penalty notices, or optimizing duties.

64

Quality

78%

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 ./skills/customs-trade-compliance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized, expert-level compliance knowledge base with genuinely actionable decision frameworks, escalation triggers, and metrics. Its weaknesses are token efficiency — substantial restatement of domain knowledge Claude already has — and the absence of any progressive disclosure: everything is inlined in a single long file rather than split into reference bundles.

Suggestions

Split reference-grade material (GRI rule walkthrough, Incoterms definitions, regional specialties, edge cases) into one-level-deep files under references/ and keep SKILL.md as an overview with clearly signaled links, e.g. 'Incoterms compliance details: See [INCOTERMS.md](references/INCOTERMS.md)'.

Trim the textbook explanations of concepts Claude already knows (Incoterms definitions, GRI basics, what the HS is) down to only the non-obvious compliance implications — the pitfalls, valuation circularity, and misunderstanding callouts.

Expand the 'Key Templates' section into fully copy-paste-ready skeletons (complete subject lines, body structure, required fields) instead of brief sketches, or move them to a references file where full versions can live without bloating the main file.

DimensionReasoningScore

Conciseness

The body is dense rather than padded, but several sections restate knowledge Claude already has — textbook Incoterms definitions ('EXW: Seller's minimum obligation. Buyer arranges everything'), the GRI walkthrough with standard examples ('A car body without the engine is still classified as a motor vehicle'), and 'The Harmonized System is a 6-digit international nomenclature maintained by the WCO.' Not 2: nearly every restatement is compressed and carries a compliance-specific caveat; not 4: the Incoterms and GRI sections could be trimmed to only the non-obvious compliance implications.

3 / 5

Actionability

Concrete, executable guidance throughout: numbered decision frameworks ('Matches below 85% name similarity with no address or country correlation are likely false positives — document and clear'), penalty formulas, an escalation table with timelines, and message templates. Not 5: the templates are explicitly brief sketches to adapt rather than copy-paste ready, and there is no executable code or commands.

4 / 5

Workflow Clarity

The multi-step processes ('Classification Decision Logic', 'FTA Qualification Analysis', 'Valuation Method Selection', 'Screening Hit Assessment') are clearly sequenced with checkpoints such as 'Validate at the subheading level' and 'Check for binding rulings.' Not 5: there are no explicit validate-then-retry feedback loops for error recovery, though this is an advisory skill rather than a destructive/batch one.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a ~240-line monolith that inlines reference-grade material — regional specialties, eight edge cases, penalty frameworks, templates — that belongs in separate one-level-deep reference files. Not 2: sections are well-organized with clear headers and the body explicitly frames itself as summaries to expand; not 4: nothing is split out of SKILL.md, and 'Additional Resources' points to internal artifacts rather than actual bundle files.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description: specific, third-person, comprehensive on capabilities, with an explicit and concrete 'Use when' trigger clause covering classification, documentation, screening, audits, and duty optimization. Keyword coverage is good though not exhaustive of every natural synonym.

Suggestions

Add a few more natural user phrasings to the trigger clause, such as 'customs broker coordination', 'tariff codes', or plain 'imports/exports', to broaden keyword matching.

DimensionReasoningScore

Specificity

The description enumerates multiple specific concrete capabilities — 'HS/HTS tariff classification with GRI rules', 'commercial invoices and entry documentation', 'FTA qualification and duty optimization (USMCA, RCEP, FTZs, drawback)', 'denied-party screening', 'penalty mitigation' — with no real coverage gaps, matching the comprehensive anchor.

5 / 5

Completeness

It clearly answers both 'what' (the enumerated capability domains) and 'when' (an explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

'Use when classifying goods, preparing import/export documentation, screening restricted parties, responding to customs audits or CF-28/penalty notices, or optimizing duties' provides good natural keyword coverage, but a few common user phrasings (e.g., 'customs broker', 'tariff codes', 'imports/exports') are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — 'CF-28/penalty notices', 'USMCA, RCEP, FTZs, drawback', 'denied-party screening' — that would rarely fire for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.