CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

track-tariff-trends

Retrieve a country's average applied tariff over time — the MFN rate on all products, or the rate it applies on goods from one partner and/or in one product group — plus the optional US effective tariff rate. Use when the user asks how a country's tariffs have changed, or what it charges another country on average. For one product between two countries, use lookup-bilateral-tariff.

Quality

94%

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

SKILL.md
Quality
Evals
Security

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 lean, highly actionable API skill: executable examples, precise parameter and response semantics, explicit entitlement and error handling, and a content-safety guard. The only structural improvement left is offloading the exhaustive HS product-group catalog into a reference file to slim the main body.

DimensionReasoningScore

Conciseness

The body is dense and lean: no explanation of concepts Claude already knows (no "what a tariff is", no library tutorials), every section carries operational facts (series selection rules, parameter semantics, field meanings, error codes). It assumes competence and every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

Two fully executable, copy-paste-ready curl examples cover the two main cases (MFN series; WITS partner+product-group series), with a concrete endpoint, auth header format, parameter table with exact values and edge-case behaviors, a complete response shape, and per-error-code remedies ("429 — rate limited; retry with backoff").

5 / 5

Workflow Clarity

This is a simple, single-action API-lookup skill with no destructive or batch operations, so the simple-skill exception applies: the sequence (authenticate → endpoint → parameters → interpret response → handle errors) is unambiguous and coherently ordered, and response-interpretation pitfalls (indicatorCode variants, unavailableReason semantics, free-tier behavior) are explicitly pre-empted.

5 / 5

Progressive Disclosure

Structure is good — clear section headers with content appropriately placed for a single-file skill, and no bundle files exist to reference (references/scripts/assets are absent), so nothing is misfiled. It sits at ~110 lines with the full HS-section enumeration and extended parameter notes inlined; that reference-like catalog could live in a references/ file, which is the minor organization gap separating it from the 5 anchor.

4 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: concrete capabilities in third person, an explicit "Use when" trigger clause with natural phrasing, and an explicit disambiguation pointer to a sibling skill. The only minor gap is absence of synonyms like "customs duty" among trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct capabilities: "Retrieve a country's average applied tariff over time — the MFN rate on all products, or the rate it applies on goods from one partner and/or in one product group — plus the optional US effective tariff rate." These are specific actions with comprehensive coverage of the operation's variants, matching the score-5 anchor.

5 / 5

Completeness

It explicitly answers both questions: the "what" is "Retrieve a country's average applied tariff over time..." with concrete variants, and the "when" is an explicit "Use when the user asks how a country's tariffs have changed, or what it charges another country on average" — matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "how a country's tariffs have changed", "what it charges another country on average", "average applied tariff", "MFN rate". Coverage is good but misses a few natural synonyms users might use, such as "duty", "customs duties", or "tariff history", keeping it just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (country-level average tariff time series) and actively reduces conflict risk with the boundary clause "For one product between two countries, use lookup-bilateral-tariff", which mirrors the boundary guidance pattern of the best examples. Minimal overlap risk remains.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

koala73/worldmonitor

Path

skills/track-tariff-trends/SKILL.md

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.