CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-data

Retrieve official statistics from public international organizations and economic-data providers.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/open-data/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a compact, well-structured instruction skill with a clear workflow, meaningful validation gates, and firm boundaries — it respects the token budget and is easy to navigate. Its main weakness is actionability: guidance stays at the checklist level with no concrete API examples, named sources, or tool invocation patterns that would make it immediately executable.

Suggestions

Add one concrete example of an official API call or source pattern (e.g., a World Bank API v2 endpoint with parameters, or an IMF SDMX query) so the 'Locate an official public API' step is executable rather than aspirational.

Show a worked mini-example of the documentation output — source URL, indicator code, unit, update date, transformation — so step 5 has a concrete template.

Embed the completion gates into the workflow as explicit validation steps with a recovery path (e.g., 'if a series break or provisional flag is found, note it and check for a revised series') to add a feedback loop.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows; every section carries operational weight. Minor trimmable content — the Purpose section repeats the frontmatter description verbatim and the copyright line adds nothing instructional — keeps it just below the 'every token earns its place' anchor of 5.

4 / 5

Actionability

As an instruction-only skill it gives a concrete capture checklist (indicator codes, dimensions, unit, update date, transformation) and a tool routing table, but no executable specifics: no example API call, no named endpoints or sources, and no sample invocation of web_fetch or render_chart. This matches 'some concrete guidance but incomplete' rather than the mostly-executable profile of a 4.

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced and the 'Completion gates' section supplies validation checkpoints (series breaks, provisional flags, seasonal adjustment, missing values), and the operation is non-destructive so the batch-validation cap does not apply. It falls short of 5 because the gates are listed separately from the steps and there is no error-recovery feedback loop (e.g., what to do when a series break or missing value is found).

4 / 5

Progressive Disclosure

The body is under 50 lines with no external reference files in the bundle (references/, scripts/, assets/ are absent) and no content that clearly belongs in separate files. Per the rubric's simple-skill exception, its well-organized sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) merit a 5.

5 / 5

Total

16

/

20

Passed

Description

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

The description is concise and names a clear, specific domain, but it states only a single generic action and provides no 'when to use' trigger guidance, which caps completeness and weakens trigger quality. All dimensions land at the midpoint: a clear 'what' with no 'when' and moderate distinctiveness from generic data-retrieval skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for official statistics, macroeconomic indicators, or data from organizations like the World Bank, IMF, OECD, or Eurostat.'

Enumerate the concrete actions the skill performs — e.g., 'fetch indicator series via official APIs, capture codes and metadata, normalize comparable series, and document sources' — to raise specificity.

Include natural synonyms and organization names users actually say (World Bank, IMF, OECD, Eurostat, GDP, unemployment rate) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description names a concrete domain ('official statistics from public international organizations and economic-data providers') and a single action ('Retrieve'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions (e.g., fetch via API, normalize series, document sources), so it is not a 4.

3 / 5

Completeness

It clearly answers 'what' (retrieve official statistics from international organizations and economic-data providers) but has no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines cap at 3. It is not a 2 because the 'what' is specific rather than vague, and not a 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Phrases like 'official statistics' and 'economic-data providers' are relevant keywords, but common natural variations users would say — organization names (World Bank, IMF, OECD, Eurostat) or terms like 'GDP data', 'indicators', 'time series' — are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The niche (official/authoritative statistics) is somewhat specific, but the generic action 'Retrieve ... data' could overlap with general web-search, data-fetching, or API-calling skills, and no distinct trigger phrases separate it. It sits between the overlap risk of a 3 and the mostly-distinct profile of a 4, fitting the 3 anchor better given the absence of distinguishing triggers.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

KunAgent/Kun

Path

resources/bundled-skills/open-data/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.