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

87%

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

88%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-reference skill body: fully executable curl example, complete parameter and response documentation, explicit error handling, a prompt-injection guard for response data, and clear routing to sibling skills. The only refinements are trimming the redundant opening paragraph and moving the detailed reference material to a separate file.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean tables and executable code with no padding or explanation of concepts Claude already knows. It is not a 5 because the opening paragraph ("Use this skill when the user asks about strategic commodity flows...") restates trigger information already present in the frontmatter description and could be trimmed.	4 / 5
Actionability	Everything is copy-paste ready: the exact endpoint URL, the auth header format with a concrete key example, a parameter table with concrete values (HS codes, reporter codes), a full response JSON shape, and a complete executable curl example with jq post-processing. This matches the fully-executable anchor.	5 / 5
Workflow Clarity	This is a simple single-action skill (an authenticated GET), and the action is unambiguous: authenticate with the X-WorldMonitor-Key header, call the endpoint, interpret the documented response and error codes (401/403/429, upstreamUnavailable). Error-recovery guidance is explicit (retry with backoff), and the read-only operation triggers no destructive/batch validation cap.	5 / 5
Progressive Disclosure	Sections are clearly organized and external references (OpenAPI operation, auth matrix) are well-signaled and one level deep. It is not a 5 because at roughly 90 lines the full parameter and response reference is inlined rather than split into a separate reference file, sitting above the 'under 50 lines' simple-skill threshold.	4 / 5
	Total	18 / 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: it pairs a concrete capability statement with an explicit 'Use when' clause containing three natural trigger phrases. Its only weakness is modest action coverage (a single retrieve action) and some missing natural synonyms (exports/imports).

Dimension	Reasoning	Score
Specificity	"Retrieve strategic UN Comtrade commodity flows with anomaly flags" names a specific domain and one concrete action (retrieve with anomaly flags), but does not list several actions, matching the '1-2 concrete actions, not comprehensive' anchor. It is not a 4 because no additional specific operations are enumerated.	3 / 5
Completeness	The description explicitly answers both questions: "Retrieve strategic UN Comtrade commodity flows with anomaly flags" (what) and "Use when the user asks who trades a critical commodity, which flows changed sharply, or how trade exposure is shifting" (when, with three concrete trigger phrases). This matches the anchor-5 good example structure exactly.	5 / 5
Trigger Term Quality	"who trades a critical commodity", "which flows changed sharply", and "how trade exposure is shifting" are natural phrases users would say, but common synonyms like "exports", "imports", or "trade data" are missing. Good coverage without being comprehensive places it at the anchor-4 example level.	4 / 5
Distinctiveness Conflict Risk	"UN Comtrade commodity flows with anomaly flags" plus triggers like "who trades a critical commodity" and "which flows changed sharply" carve out a clear niche distinct from adjacent trade/tariff skills. Conflict risk is minimal, matching the clear-niche anchor.	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: 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.