CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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 ./skills/fetch-country-brief/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, fully executable reference for a single API: exact endpoint, auth rules, parameter constraints, runnable curl examples, explicit error recovery, and clear routing between the UI tool and the text endpoint, plus a sensible prompt-injection guard. The only trims available are minor explanatory asides.

DimensionReasoningScore

Conciseness

Nearly every section conveys operative knowledge Claude cannot already know (endpoint URL, auth header, parameter shapes, error semantics), with no padded conceptual explanations. The only minor over-explanation is the parenthetical "(the classic indirect prompt-injection vector)" and similar asides, which could be trimmed, matching the 4 anchor of efficient content with minor instances to cut.

4 / 5

Actionability

The skill provides copy-paste-ready curl commands covering both the basic and the framework-parameterized cases, an exact endpoint, a parameter table with shapes and constraints, a concrete response example, and per-status error remediation. This matches the 5 anchor of fully executable commands with examples covering the common cases.

5 / 5

Workflow Clarity

The routing decision is unambiguous (UI-capable host → open_country_brief; explicit text-only or no embedded UI → get_country_brief/endpoint), with a fallback when select_country_view is unavailable and explicit recovery loops (backoff on 429, retry once after 2s on 5xx). As a simple single-action skill with unambiguous routing and explicit error handling, it meets the 5 anchor's feedback-loop standard.

5 / 5

Progressive Disclosure

The ~80-line body is appropriately self-contained for a single API, cleanly sectioned (Authentication, Endpoint, Parameters, Response shape, Worked example, Content safety, Errors, When NOT to use), with external links isolated in a clearly labeled References section. No content belongs in a separate file and navigation is trivial, matching the 5 anchor of well-organized, appropriately split content.

5 / 5

Total

19

/

20

Passed

Description

53%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 product domain and two actions, but lacks an explicit "Use when..." invocation trigger and the natural vocabulary ("country brief") a user would employ. It is serviceable but below the standard of the good examples, which pair concrete capabilities with explicit trigger phrases.

Suggestions

Add an explicit trigger clause such as "Use when the user asks for a country brief, country assessment, or analysis of a specific country" to answer the "when" question directly.

Include the natural user phrases "country brief" and "country assessment" among the keywords so trigger matching works on the vocabulary users actually say.

Enumerate the concrete capabilities available (e.g., resilience, security, economy, resources topics and dated observations) to broaden the stated action coverage.

DimensionReasoningScore

Specificity

The description names the domain ("WorldMonitor country interface") and exactly two actions ("Open the WorldMonitor country interface", "Use the text assessment endpoint"), which matches the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it is not a 4.

3 / 5

Completeness

The "what" is clear, but there is no "Use when..." trigger clause; the conditional "for explicit text-only requests or clients without embedded UI" governs which mode to use, not when to invoke the skill at all. Per the guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "country", "text assessment", and "UI-capable MCP host" are present, but the natural phrases a user would actually say ("country brief", "country report", "briefing on Iran") are missing. This gives some relevant keywords with missing common variations, matching the 3 anchor rather than the fuller coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The proprietary "WorldMonitor" name gives a clear niche with minimal conflict risk against generic skills, but the trigger terms themselves are weak and would not clearly distinguish it from other country-analysis skills, so it falls between the distinct-niche 5 and the somewhat-specific 3, noticeably above the midpoint.

4 / 5

Total

13

/

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/fetch-country-brief/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.