CtrlK
BlogDocsLog inGet started
Tessl Logo

fetch-country-brief

Open the WorldMonitor country interface in a UI-capable MCP host. Use the text assessment endpoint for explicit text-only requests or clients without embedded UI.

60

Quality

75%

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 ./public/.well-known/agent-skills/fetch-country-brief/SKILL.md

The canonical home for this skill is fetch-country-brief in koala73/worldmonitor

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a strong, lean API skill: concrete tool names, an executable worked example, precise parameter and error documentation, and a well-placed content-safety note. Only minor refinements remain — trimming a couple of tangential asides and adding an explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is efficient — tables, exact endpoints, and copy-paste curl examples with no filler — but has minor trimmable asides such as the CORS/browser free-pass note that agents never hit.

4 / 5

Actionability

Fully executable guidance: exact tool names (open_country_brief, select_country_view), a complete valid-topic list, the endpoint URL, a params table with edge-case notes, response shape, and two copy-paste-ready curl examples covering the common cases.

5 / 5

Workflow Clarity

The sequence (open interface → follow-up via select_country_view → fallback text endpoint) is clear, and error handling includes recovery guidance ("retry with backoff", "retry once after 2s"); not a destructive/batch operation, though no explicit feedback loop for 400/401 diagnosis is provided.

4 / 5

Progressive Disclosure

A single compact file with well-organized sections and clearly signaled one-level external references (OpenAPI, auth matrix). At ~85 lines it exceeds the under-50-line simple-skill bound, and some API reference material (params/response) is inline, but structure and navigation are good.

4 / 5

Total

17

/

20

Passed

Description

57%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 identifies a distinct, brand-specific niche with two concrete actions, but lacks an explicit "Use when..." trigger for the primary path and omits the natural user phrasing ("country brief") that would drive skill selection. It sits just above the midpoint of quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a country brief or country intelligence/report on a specific nation."

Include natural synonyms users would say — "country brief", "country report", "intelligence on [country]" — rather than only the technical term "country interface".

Briefly mention the follow-up capability (topic selection) so the description covers the skill's full scope, not just the initial open action.

DimensionReasoningScore

Specificity

"Open the WorldMonitor country interface" and "Use the text assessment endpoint" name the domain and two concrete actions, but coverage is not comprehensive — follow-up navigation, topics, and brief retrieval are absent.

3 / 5

Completeness

The "what" is clear, but the only "when" guidance covers the fallback path ("for explicit text-only requests or clients without embedded UI") with no trigger clause for the primary path, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like "WorldMonitor", "country interface", and "text assessment" are present, but the natural phrases users would say ("country brief", "country report") are missing; "brief" appears only in the skill name, not the description.

3 / 5

Distinctiveness Conflict Risk

"WorldMonitor country interface" defines a clear brand-specific niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.