CtrlK
BlogDocsLog inGet started
Tessl Logo

compare-macro-history

Compare CPI, interest rates and sovereign yield histories from seeded official reports. Use for inflation or rate trends; preserve country provenance, index base, frequency, yield measure and missing readings.

72

Quality

90%

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

The canonical home for this skill is compare-macro-history in koala73/worldmonitor

SKILL.md
Quality
Evals
Security

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.

The body is an exemplary lean instruction skill: concrete tool and REST details, a copy-paste request example, explicit data-handling rules (unknown vs zero, truncation, provenance), error/retry policy, and injection-defense guidance, all in well-organized sections with zero padding. No weaknesses surfaced against any dimension.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: it never explains what CPI or yields are, and every line carries operational facts (dataset table, "limit defaults to 30 and accepts 1..365", response shape, routes, auth header, error policy). This matches anchor 5 — every token earns its place; nothing matches the padding of anchors 3–4.

5 / 5

Actionability

Guidance is fully concrete: the tool name `get_macro_history` with server URL, a dataset table with required parameters, a copy-paste request example ("{\"dataset\":\"world-cpi\",\"country\":\"Germany\",\"limit\":12}"), exact REST routes, and the precise auth header "X-WorldMonitor-Key". Per the rubric's code_vs_instruction note, an instruction-only skill with guidance this specific is not penalized for lacking code; it matches anchor 5's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

The flow is sequenced with explicit checkpoints: "Read `unavailable` first", "`truncated: true` means the response is not full history", "request one country at a time and align observation dates and definitions before comparing", and the worked example ends with comparing on common dates, explaining methodology differences, and citing source labels. Retry guidance ("Respect billing denials, rate limits and `Retry-After`") covers error recovery; the destructive/batch cap does not apply to read-only retrieval, and the under-50-line simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and the body is cleanly sectioned (Connected plugin, REST and authentication, Errors, Content safety) with no dangling or buried references. Per the judging guidelines, this matches the simple-skill case where well-organized sections alone score 5.

5 / 5

Total

20

/

20

Passed

Description

78%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 two-sentence description in third person: it states concrete capabilities with an explicit "Use for..." trigger clause and is highly distinct from other skills. The main gaps are missing yield-oriented trigger synonyms (bond/treasury yields, yield curve) and a when-clause that does not cover the yield datasets.

Suggestions

Extend the trigger clause to cover the yield use case, e.g. "Use for inflation, interest-rate, or sovereign/bond yield trend questions over time" so the 'when' explicitly spans all three dataset families.

Add natural synonyms users would say — "bond yields", "treasury yields", "yield curve" — to the trigger terms so queries phrased with those words surface the skill.

DimensionReasoningScore

Specificity

The description names concrete, specific actions — "Compare CPI, interest rates and sovereign yield histories from seeded official reports" and "preserve country provenance, index base, frequency, yield measure and missing readings" — with named objects rather than vague language. It falls short of anchor 5 because it is dominated by a single compare verb with a data-handling clause, rather than a comprehensive list of multiple distinct actions.

4 / 5

Completeness

Both parts are explicit: the what ("Compare CPI, interest rates and sovereign yield histories from seeded official reports") and the when ("Use for inflation or rate trends"). It matches anchor 4 rather than 5 because the when-clause omits trigger phrases for the yield datasets — a third of the skill's coverage — so the 'when' could be more explicit and specific.

4 / 5

Trigger Term Quality

Natural user terms are present — "inflation", "rate trends", "CPI", "interest rates", "sovereign yield" — giving good keyword coverage anchored by an explicit trigger clause. It is not 5 because common synonyms users would say are missing, such as "bond yields", "treasury yields", "yield curve", or "over time"; it is above 3 because coverage goes beyond merely relevant keywords.

4 / 5

Distinctiveness Conflict Risk

"CPI, interest rates and sovereign yield histories from seeded official reports" carves out a clear niche with distinct triggers and near-zero overlap with generic data or document skills. It clearly matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

17

/

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