CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-destination-section

Read one published section of 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/govisit-destination/skills/govisit-get-destination-section/SKILL.md

The canonical home for this skill is govisit-get-destination-section in inhotel-io/govisit-toolkit

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.

A well-structured, highly actionable skill body with excellent progressive disclosure and thorough error-handling guidance for a single HTTP call. The main cost is administrative padding: version digests, update mechanics, and licensing detail repeat frontmatter data and spend tokens without aiding execution.

Suggestions

Trim the 'Source and updates' section: drop the repeated version string and source digest (already in frontmatter) and compress installer/update instructions to a single line pointing at the canonical URL.

Reduce the 'Licensing' section to a one-line MIT note plus the data-use license link.

Clarify the request construction by stating once that the JSON body is exactly the tool arguments (pagePath and section), removing the redundant restatement.

DimensionReasoningScore

Conciseness

The core call and response-handling guidance is lean and operational, but the 'Source and updates' and 'Licensing' sections repeat the version number and source digest already present in frontmatter and add installer/distribution detail that does not guide execution. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

It gives a fully specified executable call: exact endpoint, method, Content-Type, a copy-paste JSON body, and a per-status-code error table (400/413/415, 404, 429 with Retry-After, 503). It falls short of 5 only because 'Send the tool arguments directly as the JSON body' alongside 'The HTTP body requires pagePath plus the tool arguments' is slightly redundant and no literal command example (e.g., curl) is given.

4 / 5

Workflow Clarity

The single action (one HTTPS POST) is unambiguous, and error recovery is explicitly mapped (invalid-input means correct the arguments; 429 means wait for Retry-After; avoid unbounded retries). It does not reach 5 because transitions like consulting the contract and validating section support are implicit rather than presented as an explicit checkpoint sequence.

4 / 5

Progressive Disclosure

The body is a well-organized overview that keeps the input/output schemas in references/contract.json, referenced exactly once with a clear link and a description of what it contains ('exact input and output JSON schemas, supported fields, and defaults'). The bundle confirms one level of depth with no nested references, matching the 'clear overview with well-signaled one-level-deep references' anchor.

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.

A serviceable description with an explicit 'Use when' clause and a distinct branded niche, but it names only a single action and lacks the natural trigger phrases users would actually utter. Broadening the concrete actions and adding user-facing synonyms would strengthen it.

Suggestions

Enumerate the concrete capability more fully, e.g. name the supported sections (overview, experiences, highlights, places) instead of only 'Read one published section'.

Add natural trigger phrases users would say, such as 'destination guide', 'things to do', or 'GoVisit page data', to improve trigger term coverage.

Tighten the when-clause to concrete triggers ('Use when resolving a GoVisit destination link or checking published destination content for a travel decision').

DimensionReasoningScore

Specificity

The description names its domain ("published section of the selected destination") and one concrete action ("Read one published section"), but offers no broader list of concrete capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. It is not score 4 because it never enumerates several specific actions.

3 / 5

Completeness

It explicitly answers both: what ("Read one published section of the selected destination") and when ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision"). The when-clause is explicit but somewhat abstract ('needs this published GoVisit evidence through HTTP'), so it does not reach the concrete-trigger-phrases level of a 5.

4 / 5

Trigger Term Quality

Relevant keywords exist ("destination", "GoVisit", "travel decision", "integration"), but common natural variations a user would say (e.g., "things to do", "destination guide", "attractions") are absent. It sits at 'some relevant keywords but missing common variations', below the 'good coverage' anchor.

3 / 5

Distinctiveness Conflict Risk

The GoVisit branding and narrow tool scope ('get_destination_section', 'published section') create a clear niche with minimal conflict risk. However, the broad trigger 'travel decision' could overlap with other travel-related skills, keeping it below the 'minimal conflict risk' anchor.

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

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