>
73
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 a strong skill description that clearly defines a specific domain (international trade compliance and customs), lists multiple concrete capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. The only minor weakness is the credential claim ('15+ years experience') which is unnecessary filler, but it doesn't detract significantly from the description's functional quality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: customs documentation, tariff classification, duty optimization, restricted party screening, regulatory compliance, HS classification logic, Incoterms application, FTA utilization, and penalty mitigation. | 3 / 3 |
Completeness | Clearly answers both 'what' (customs documentation, tariff classification, duty optimization, restricted party screening, regulatory compliance, HS classification, Incoterms, FTA utilization, penalty mitigation) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'customs clearance', 'tariff classification', 'trade compliance', 'import/export documentation', 'duty optimization', 'HS classification', 'Incoterms', 'FTA', 'restricted party screening'. These cover a wide range of natural user queries in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche in international trade compliance and customs. The specific domain terminology (HS classification, Incoterms, FTA, restricted party screening) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
39%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a comprehensive trade compliance textbook rather than a concise, actionable skill file. Its greatest strength is workflow clarity—the decision frameworks are well-sequenced with validation steps and escalation protocols. However, it is severely undermined by extreme verbosity (explaining foundational concepts Claude already knows), lack of executable artifacts, and a monolithic structure that should be split across multiple referenced files.
Suggestions
Reduce content by 60-70%: Remove textbook explanations of GRI rules, Incoterms definitions, and WTO valuation methods. Instead, provide only the non-obvious gotchas and decision logic Claude wouldn't already know.
Split into multiple files: Move Core Knowledge sections (HS Classification, Incoterms, Valuation, etc.) into separate reference files (e.g., HS_CLASSIFICATION.md, INCOTERMS.md) and link from the main SKILL.md with clear one-level-deep references.
Add concrete, executable artifacts: Include actual template text for prior disclosure filings, broker instruction emails, and CF-28 response letters rather than describing what they should contain.
Convert the Key Edge Cases and Regional Specialties sections into linked reference files, keeping only a brief summary table in the main skill with pointers to detailed guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~3500+ words, extensively explaining concepts Claude already knows (GRI rules, Incoterms definitions, WTO valuation methods, HS code structure). Much of this is textbook-level trade compliance knowledge that doesn't need to be spelled out in full. The content reads like a training manual rather than a concise skill reference. | 1 / 3 |
Actionability | The skill provides structured decision frameworks (classification logic, FTA qualification steps, screening hit assessment) with specific regulatory references and thresholds, which is useful. However, there are no executable code examples, no API calls, no concrete tool commands, and the guidance remains at the procedural/conceptual level rather than providing copy-paste-ready artifacts like actual filing templates or screening scripts. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit ordering (classification decision logic, FTA qualification analysis, valuation method selection, screening hit assessment). Validation checkpoints are present (e.g., 'document the rationale,' 'never proceed while a screening hit is unresolved'), escalation triggers have specific timelines, and the screening workflow includes a clear feedback loop for false positive resolution. | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. All content—core knowledge, decision frameworks, edge cases, communication patterns, escalation protocols, KPIs—is inlined in a single massive document. The 'Additional Resources' section vaguely suggests pairing with other documents but provides no links or file references. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
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 | 8 / 11 Passed | |
Reviewed
Table of Contents