CtrlK
BlogDocsLog inGet started
Tessl Logo

customs-trade-compliance

Codified expertise for customs documentation, tariff classification, duty optimization, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilization, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimization.

63

Quality

75%

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

The canonical home for this skill is tdg-personal/customs-trade-compliance

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.

A richly detailed, well-structured knowledge skill with concrete decision frameworks and worked examples. Its main weaknesses are token weight (a long monolithic body) and the absence of progressive disclosure via reference files.

Suggestions

Move the exhaustive GRI rule list, US penalty-tier breakdowns, and regional specialties into separate reference files (e.g., references/gri-rules.md, references/regional-specialties.md) and link to them from the body to improve both conciseness and progressive disclosure.

Extract the communication templates and escalation table into a references/templates.md file, keeping only a brief pointer inline in SKILL.md.

Add explicit validation feedback loops to the classification and FTA workflows (e.g., 'if the binding-ruling search returns a conflicting classification, re-apply GRI 3 and document the deviation') to push workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's intelligence (no basic-concept padding), but at 244 lines it could be tightened by moving exhaustive enumerations (full GRI list, all penalty tiers, regional specialties) into reference files rather than keeping them inline.

3 / 5

Actionability

Provides concrete, specific guidance — worked examples (HS dispute, FTA qualification, screening hit), step-by-step decision frameworks, and templates — that is actionable for an advisory/knowledge skill, with only minor gaps since it offers no executable commands by nature.

4 / 5

Workflow Clarity

Multi-step processes (classification logic, FTA qualification, valuation method hierarchy, screening protocol) are clearly sequenced with validation checkpoints (verify identity, check binding rulings, document rationale) and an escalation table with timelines; a few feedback loops could be more explicit.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but no bundle files exist and everything is inlined in SKILL.md; clearly separable sub-domains (regional specialties, templates, detailed GRI/penalty enumerations) remain inline rather than being split into one-level-deep references.

3 / 5

Total

14

/

20

Passed

Description

87%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, specific description with an explicit 'Use when' clause covering natural trigger terms and a well-defined niche. The only minor weakness is noun-phrase rather than verb-phrase framing of capabilities and a few missing synonyms in the trigger list.

DimensionReasoningScore

Specificity

Lists several concrete capabilities (customs documentation, tariff classification, duty optimization, restricted party screening, FTA utilization, penalty mitigation), but they are noun-phrased domains rather than verb-form actions, so it sits just below the fully comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (codified expertise for the listed customs/trade tasks) and 'when' ('Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimization') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause covers natural phrases a user would say (customs clearance, tariff classification, trade compliance, import/export documentation, duty optimization), missing a few common synonyms such as 'HS codes' or 'Incoterms' that appear only in the body.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (customs & trade compliance across jurisdictions) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

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.

Validation14 / 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.