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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

96%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 tight, executable skill body with concrete auth, parameters, response shape, and a worked example, plus useful safety and routing guidance. The only minor gap is progressive disclosure, where references are external URLs rather than an internal bundle that could be split out.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation of concepts Claude already knows; every section earns its place and the sample 'year: 2026' is illustrative data, not version-dependent instruction.	5 / 5
Actionability	Provides a fully executable curl example with headers, URL-encoded params, and a jq projection, plus a complete parameters table and concrete response schema covering the common case.	5 / 5
Workflow Clarity	The skill is a single unambiguous read-only GET retrieval, so the simple-skill exception applies; content-safety and upstreamUnavailable/error-code checkpoints provide the necessary validation for a non-destructive operation.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and clearly signaled one-level-deep references (OpenAPI and auth matrix); no internal bundle files exist, so the structure is good but lacks the split-file navigation of the top anchor.	4 / 5
	Total	19 / 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, well-formed description that pairs a concrete capability statement with explicit multi-clause trigger guidance in a distinct niche. Its only weakness is moderate action specificity, naming a single retrieve action rather than enumerating several.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Retrieve strategic UN Comtrade commodity flows with anomaly flags') but does not enumerate multiple distinct actions, so it is not comprehensive.	3 / 5
Completeness	Explicitly answers both what (retrieve commodity flows with anomaly flags) and when (three concrete trigger clauses), matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrasings ('who trades a critical commodity', 'which flows changed sharply', 'how trade exposure is shifting') with good coverage, though a few synonyms and explicit commodity names are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (strategic UN Comtrade commodity flows) with distinct triggers and minimal overlap with adjacent tariff/restriction skills.	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: 23ab7d1

Reviewed: 2 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.