CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-search-places

Search GoVisit places by name or traveler intent, optionally constrained by country, destination, or proximity. Use when a traveler needs candidate places and canonical profile URLs.

Quality

82%

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

77%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 well-structured, highly actionable single-purpose skill whose calling guidance, error handling, and reference split are exemplary. The main drag is token efficiency: the 'Source and updates' and licensing sections duplicate frontmatter metadata and repeat URLs already stated elsewhere.

Suggestions

Trim the 'Source and updates' section: the version hash and source digest are already in the frontmatter, so the body can simply point to the canonical URL and the discovery index without restating them.

State the contract reference once with a single URL (either the bundled path or the web URL) instead of giving both inline and again in 'Source and updates'.

Add a one-line ready-to-use request example (e.g., a curl command) or a second JSON example covering 'auto'/'intent' mode to close the small actionability gap.

DimensionReasoningScore

Conciseness

The instructional sections ('Call the tool', 'Interpret the response') are dense and assumption-respecting, but the 'Source and updates' section repeats the version hash and source digest already present in frontmatter, and the canonical and contract URLs each appear twice in the body. Time-sensitive version identifiers are not confined to a deprecation-style section, so the body could be meaningfully tightened.

3 / 5

Actionability

Concrete, executable guidance throughout: exact endpoint and method ('HTTPS POST request to https://govisit.ai/api/tools/v1/search_places with Content-Type: application/json'), a complete JSON request body, mode-specific limits, and per-status error semantics (400/413/415, 404, 429 with Retry-After, 503). Minor gaps keep it below 5: no ready-made request command (e.g., a curl line) and only the 'name' mode is exemplified.

4 / 5

Workflow Clarity

For this single-task skill the sequence is unambiguous — build arguments per the contract, make one POST, interpret data.items, then verify — with explicit checkpoints and feedback loops: 'Open returned canonical URLs to inspect published evidence before making claims', 'invalid-input means correct the arguments', '429 requires waiting for Retry-After', and 'Avoid unbounded retries'. This matches the anchor-5 pattern of explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

The body is a lean overview that defers exact schemas to a single clearly 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 that file exists in the bundle and matches the described endpoint. Sections are well organized with no nested-reference chains.

5 / 5

Total

17

/

20

Passed

Description

78%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 tight, third-person description that states concrete capabilities and includes an explicit 'Use when' trigger clause tied to a distinctive niche. Its only weaknesses are slightly jargon-heavy trigger phrasing and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities — 'Search GoVisit places by name or traveler intent, optionally constrained by country, destination, or proximity' plus 'canonical profile URLs' — with only minor gaps. It stops short of anchor 5 because it describes one search action with modifiers rather than a comprehensive list of multiple distinct concrete actions.

4 / 5

Completeness

Both halves are explicit: a clear 'what' ('Search GoVisit places by name or traveler intent, optionally constrained by...') and an explicit 'Use when a traveler needs candidate places and canonical profile URLs' clause. It does not reach 5 because the when-clause uses internal jargon ('candidate places and canonical profile URLs') rather than concrete, user-facing trigger phrases.

4 / 5

Trigger Term Quality

Natural terms a user or agent would say are present: 'search', 'places', 'name', 'traveler intent', 'country', 'destination', 'proximity'. A few natural variations are missing (e.g., 'find', 'attractions', 'nearby'), keeping it below comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

The description is bound to a clearly named niche ('GoVisit places', 'canonical profile URLs') with distinct triggers, so overlap with generic search or maps skills is minimal — a clean match for the anchor-5 example of a clear niche with distinct triggers.

5 / 5

Total

17

/

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-places/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.