CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-search-destinations

Search GoVisit destinations by name or traveler intent and return canonical destination codes and URLs. Use when a traveler needs to identify or explore a country, region, district, city, or highlight.

Quality

92%

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

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.

A highly actionable, well-structured single-tool skill: the request recipe is copy-paste ready, error handling maps each failure to a concrete remedy, and schema detail is properly externalized to a real one-level-deep reference file. The only drag is administrative sections (source digests, licensing URLs) that duplicate frontmatter metadata and could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The core sections are dense and assume Claude's competence ("No authentication, MCP framing, SSE connection, cookies, or session is required"; precise per-code HTTP error semantics), but the "Source and updates" and "Licensing" sections repeat version digests already in the frontmatter and add administrative tokens that could be trimmed, matching the 4 anchor rather than 5's "every token earns its place".

4 / 5

Actionability

Fully executable guidance: the exact endpoint and Content-Type, a complete copy-paste JSON body ("query": "Prague", "mode": "name", "language": "en", "limit": 5), and specific per-error remedies (429 requires waiting for `Retry-After`; 400/413/415 require correcting the request). This matches the 5 anchor; there are no gaps in the common path that would justify 4.

5 / 5

Workflow Clarity

A single-task skill with an unambiguous call structure ("Call the tool" → "Interpret the response"), explicit error-recovery mapping ("invalid-input means correct the arguments"; "Avoid unbounded retries"), and a pre-claim checkpoint ("Open returned canonical URLs to inspect published evidence before making claims"). The operation is read-only, so the destructive/batch cap does not apply, and the simple-skill exception for a 5 fits.

5 / 5

Progressive Disclosure

A clear overview with one well-signaled, one-level-deep reference — "Read [references/contract.json](references/contract.json) for the exact input and output JSON schemas, supported fields, and defaults" — and the bundle confirms that file exists and holds exactly those schemas (inputSchema, output, errorSchema). This matches the 5 anchor; the reference is clearly signaled and the content split is appropriate, so 4's "minor organization gaps" does not apply.

5 / 5

Total

19

/

20

Passed

Description

87%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 description with clear what/when structure, third-person voice, and a well-anchored platform niche. The only weaknesses are minor: capability coverage skips containment filtering and highlight classification, and a few natural travel synonyms are absent from the trigger terms.

DimensionReasoningScore

Specificity

"Search GoVisit destinations by name or traveler intent and return canonical destination codes and URLs" lists several concrete actions (name search, intent search, code/URL return), but omits tool capabilities such as containment filtering (within) and highlight classification, matching the 4 anchor's minor coverage gaps rather than 5's comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: what — "Search GoVisit destinations... and return canonical destination codes and URLs"; when — "Use when a traveler needs to identify or explore a country, region, district, city, or highlight" with concrete trigger contexts. This clearly matches the 5 anchor; it is not 4 because the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Natural travel-domain nouns "country, region, district, city, or highlight" plus "traveler intent" provide good keyword coverage, but common user synonyms like "place", "location", or "where to go" are missing, matching the 4 anchor rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"GoVisit destinations" pins a clear niche with distinct triggers (canonical destination codes, URLs, destination taxonomy), giving minimal conflict risk; the platform anchoring makes it more distinct than the 4 anchor's "minor overlap risk with closely related skills".

5 / 5

Total

18

/

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

inhotel-io/govisit-toolkit

Path

skills/govisit-search-destinations/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.