CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-destination-overview

Read the published overview fields for the selected destination. Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision.

Quality

73%

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/govisit-get-destination-overview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, single-purpose skill with strong executable guidance, thorough error-handling directions, and exemplary use of a one-level-deep reference file. Its main weaknesses are moderate redundancy (repeated canonical URLs and provenance details that duplicate frontmatter) and one ambiguous sentence about the request body, which cost it conciseness and a point of workflow clarity.

Suggestions

Deduplicate the URLs and provenance: drop the repeated canonical URL, the second inline contract URL, and the version/digest paragraph that restates frontmatter metadata — link them once instead.

Clarify or remove 'The HTTP body requires pagePath plus the tool arguments' since pagePath is itself the tool argument in the example; state plainly that the body is the tool's arguments object with pagePath as the required field.

Add a short sample success response (or a pointer to one in contract.json) and optionally a complete curl example to make the call fully copy-paste ready.

DimensionReasoningScore

Conciseness

Most of the body covers genuinely skill-specific knowledge (endpoint, argument rules, error semantics), but there is noticeable redundancy: the canonical URL appears in both frontmatter and the 'Source and updates' section, the contract reference URL is printed twice (as a link and again in prose), and the digest/version provenance paragraph largely repeats frontmatter metadata. This is 'mostly efficient but could be tightened' rather than the minor-trims case at 4, and it is far from the padded explanatory verbosity of the low anchors.

3 / 5

Actionability

The guidance is concrete and near-executable: an exact endpoint URL, method, content type, a JSON request body example, and per-code error handling with specific actions ('429 requires waiting for Retry-After', 'invalid-input means correct the arguments'). Minor gaps keep it below copy-paste-ready: no complete request example (e.g., a curl command) and no sample response showing the output fields in practice.

4 / 5

Workflow Clarity

As a single-purpose skill the action is well sequenced — build pagePath from a canonical link, make one POST, then interpret — with explicit error-recovery direction for each failure mode, satisfying the simple-skill path. One confusing sentence, "The HTTP body requires pagePath plus the tool arguments", appears contradictory since pagePath *is* the tool argument shown in the example, leaving a minor clarity gap that prevents the unambiguous-action top score.

4 / 5

Progressive Disclosure

The body is a concise overview and the single bundle file (references/contract.json) is referenced with a clear markdown link and an explicit statement of what it holds ("exact input and output JSON schemas, supported fields, and defaults") — a well-signaled, one-level-deep reference with no nesting. This matches the anchor for a clear overview with appropriately split content and easy navigation; the referenced file exists in the bundle.

5 / 5

Total

16

/

20

Passed

Description

62%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 follows the what-plus-when pattern with an explicit trigger clause and a distinctive GoVisit niche, but the capability statement covers only a single action and the 'when' clause leans on internal jargon ("published GoVisit evidence through HTTP") rather than natural user phrasing. It sits solidly above the vague/bad examples but below the polished good examples in both breadth and trigger naturalness.

Suggestions

Broaden the 'what' with the concrete fields or data types returned (e.g., '...including description, highlights, and practical details for a destination') to lift specificity beyond a single action.

Rewrite the 'when' clause in natural user vocabulary — e.g., 'Use when the user asks about a destination's overview, travel details, or published GoVisit page data' — to improve trigger-term quality.

Add one or two common synonyms (travel guide, place/city details) so the description triggers on phrasings users actually say.

DimensionReasoningScore

Specificity

"Read the published overview fields for the selected destination" names the domain and one concrete action, but the description stops there — it does not enumerate what the overview fields cover or any additional capabilities. This matches the anchor for naming a domain with 1-2 concrete actions without comprehensive coverage, and is below the 'several specific actions' anchor at 4.

3 / 5

Completeness

Both parts are present: 'what' is "Read the published overview fields for the selected destination" and 'when' is the explicit "Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision" clause. The 'when' is explicit but convoluted and jargon-heavy ("published GoVisit evidence through HTTP"), so it could be more natural and specific — matching the anchor where both exist but 'when' could be sharper rather than the fully concrete trigger phrases of a 5.

4 / 5

Trigger Term Quality

Relevant terms are present — "destination", "travel decision", "overview", "GoVisit" — which a user might naturally say, but common variations and synonyms (e.g., "travel guide", "place details", "city information") are missing. It has some relevant keywords but is not the comprehensive natural-term coverage of the top anchors, nor as thin as the generic one-or-two keyword anchor.

3 / 5

Distinctiveness Conflict Risk

The GoVisit-specific framing ("published GoVisit evidence", "destination overview") carves out a clear niche unlikely to fire for unrelated skills. There is minor overlap risk with other travel/destination-related skills since generic terms like "travel decision" are shared, placing it just below the minimal-conflict anchor of 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

inhotel-io/govisit-toolkit

Path

skills/govisit-get-destination-overview/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.