CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

world-bank-data

Retrieve and analyze World Bank indicators, country metadata, and development time series.

Quality

76%

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

Fix and improve this skill with Tessl

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

Quality

Content

78%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 exemplar of token-efficient, well-sectioned guidance with a clear workflow and explicit completion gates. Its one real gap is actionability: for a skill whose core operation is fetching from the World Bank API, it never provides a concrete endpoint pattern or example request.

Suggestions

Include one or two concrete example API URL patterns (e.g., the indicator-metadata and country-data endpoints) so the fetch steps are executable rather than descriptive.

Add a brief feedback loop for failed or empty fetches (e.g., retry with a corrected indicator code or fall back to browser_use) to strengthen the workflow's validation.

Provide a short worked example (one indicator, a couple of countries, the resulting comparison) to anchor the workflow's steps in a concrete case.

DimensionReasoningScore

Conciseness

The body is lean and directive with no padding or explanations of concepts Claude already knows (e.g., "Do not average region aggregates with countries", "Do not interpolate missing data without disclosure"); the only minor redundancy is the Purpose line duplicating the frontmatter description, which does not detract from the 'every token earns its place' anchor.

5 / 5

Actionability

There is some concrete guidance (a tool routing table naming web_fetch/browser_use/render_chart, an ordered workflow, and specific checks like "current versus constant prices, per-capita denominators"), but no executable specifics such as example World Bank API endpoint/URL patterns or a sample request, leaving key details missing per the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced and the 'Completion gates' section provides explicit analytical checkpoints, matching 'clear sequence with most checkpoints present'; it stops short of 5 because there is no error-recovery or feedback loop for failed or empty data fetches.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs none — content is appropriately self-contained with well-organized sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery), which per the rubric's simple-skill guideline earns a 5.

5 / 5

Total

17

/

20

Passed

Description

61%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, third-person, and firmly anchored to a distinct niche (World Bank data), with good natural trigger terms for that domain. Its main weaknesses are the absence of any 'Use when...' trigger clause and action verbs that stay generic (retrieve/analyze) rather than enumerating specific capabilities.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks about World Bank data, development indicators, or country statistics.'

Enumerate more specific actions (e.g., fetch indicator metadata, download time series, compare countries, chart trends) instead of the generic 'retrieve and analyze'.

Include common user synonyms such as 'World Bank API', 'development data', or well-known indicator examples (GDP, population) to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (World Bank data) with two concrete actions ("Retrieve and analyze") applied to specific objects (indicators, country metadata, time series), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not enumerate several specific actions, so it does not reach 4.

3 / 5

Completeness

It clearly answers 'what' ("Retrieve and analyze World Bank indicators, country metadata, and development time series") but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"World Bank", "indicators", "country metadata", and "development time series" are natural phrases users would say in this niche, giving good keyword coverage; a few natural terms are missing (e.g., "World Bank API", "development data", "country statistics"), so it falls short of the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The explicit "World Bank" anchoring gives it a clear niche with mostly distinct triggers, but the generic trailing "analyze... development time series" phrasing carries minor overlap risk with general data-analysis skills, matching 'mostly distinct; minor overlap risk' rather than the fully distinct anchor at 5.

4 / 5

Total

14

/

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/world-bank-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.