trace-trade-flows

Retrieve strategic UN Comtrade commodity flows with anomaly flags. Use when the user asks who trades a critical commodity, which flows changed sharply, or how trade exposure is shifting.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

An exemplary API-skill body: lean, entirely non-obvious content organized into scannable sections, with executable code, concrete parameter examples, full error semantics, and a content-safety guardrail. Nothing needs to be moved or trimmed.

Dimension	Reasoning	Score
Conciseness	Every section carries non-obvious, API-specific facts — auth header and its Bearer-vs-API-key distinction, entitlement gating, parameter table, response field semantics, error codes — with zero explanation of concepts Claude already knows. Nothing is padded and every token earns its place.	5 / 5
Actionability	The body is copy-paste executable: a complete curl with headers and urlencoded params, a real example key format, concrete HS/reporter code examples (842, 156, 2709, 8542), a worked JMESPath projection, a full response schema, and jq post-processing. Not 4 because there are no gaps — even rate-limit backoff and upstream-staleness semantics are specified.	5 / 5
Workflow Clarity	This is a single-call API skill whose one action is unambiguous (auth header -> endpoint -> params -> interpret response), and error-recovery guidance is explicit: 401/403/429 meanings, retry with backoff, and the caveat that 'upstreamUnavailable: true ... does not prove zero trade'. The 'When NOT to use' section adds a disambiguation checkpoint. No destructive or batch operation, so no validation cap applies.	5 / 5
Progressive Disclosure	The skill is self-contained with no bundle directories (references/, scripts/, assets/ are empty), and all inline content is appropriate for a single-endpoint skill. External references — OpenAPI operation 'ListComtradeFlows' and the auth-matrix doc — are one level deep, clearly signaled in a References section, and easy to navigate.	5 / 5
	Total	20 / 20 Passed

Description

82%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: concrete third-person what-clause paired with an explicit 'Use when' containing three natural trigger phrases. The only weakness is a thin action list — one verb ('retrieve') where a couple more specific actions would round out coverage.

Suggestions

Add one or two more concrete capabilities to the what-clause (e.g. 'filter by reporter, HS commodity code, or anomaly threshold; project responses server-side via JMESPath') to lift specificity.

Mention one or two concrete commodity trigger terms users would say (e.g. 'crude oil, gold, or semiconductor trade') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names its domain ('strategic UN Comtrade commodity flows') and one concrete action ('Retrieve ... with anomaly flags'), but offers no additional actions to be comprehensive. It sits at the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	It explicitly answers both questions: 'Retrieve strategic UN Comtrade commodity flows with anomaly flags' states the what, and 'Use when the user asks who trades a critical commodity, which flows changed sharply, or how trade exposure is shifting' gives three concrete trigger phrases. This matches the top anchor; the when is neither missing nor weakly implied.	5 / 5
Trigger Term Quality	The 'when' clause uses natural user phrasings — 'who trades a critical commodity', 'which flows changed sharply', 'how trade exposure is shifting' — that users would plausibly say verbatim. A few natural synonyms (e.g. naming oil, gold, or semiconductors, or 'trade data') are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The UN Comtrade / commodity-flow / anomaly niche is distinct and unlikely to fire for other skills, and the trigger phrases are specific rather than generic. Voice is third person ('Retrieve...'), so no voice penalty applies.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: koala73/worldmonitor
Path: public/.well-known/agent-skills/trace-trade-flows/SKILL.md
Commit: da33e7a

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.