CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-category-overview

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

Quality

75%

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-category-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 strong, actionable single-call skill guide: exact endpoint, body example, real contract reference, and a thorough error-handling map. Its main weakness is token efficiency — duplicated version/digest metadata and time-sensitive version detail in the 'Source and updates' and licensing sections could be trimmed or delegated to the reference.

Suggestions

Remove the version and source-digest repetition from the 'Source and updates' section (they already appear in frontmatter) and drop the raw digest strings from the body to save tokens.

Add one complete example request (e.g., a curl command) and a short example response to make the happy path fully copy-paste executable.

Tighten the pagePath guidance by merging the prose paragraph ('The HTTP body requires pagePath plus the tool arguments...') with the overlapping bullet list below it.

DimensionReasoningScore

Conciseness

The body is mostly dense and useful, but the 'Source and updates' section repeats the version and source digest already in frontmatter, and time-sensitive version numbers are inline rather than isolated, which the guidelines say should penalize conciseness. There is also mild redundancy between the pagePath paragraph and its following bullets, fitting 'mostly efficient but could be tightened' rather than 4.

3 / 5

Actionability

Concrete, executable guidance is present: the exact endpoint ('https://govisit.ai/api/tools/v1/get_category_overview'), content type, a JSON body example, a real contract file for schemas, and an HTTP-status-to-action error map. It stops short of 5 because no complete request or example response is shown, leaving minor gaps for copy-paste execution.

4 / 5

Workflow Clarity

The single-call workflow is clearly sequenced (build pagePath, call, interpret per output schema, handle errors) with most checkpoints present: 'invalid-input means correct the arguments', '429 requires waiting for Retry-After', and 'HTTP 400/413/415 require correcting the request'. It is not 5 because the recovery steps are mapped but not assembled into an explicit ordered procedure with a re-validate loop.

4 / 5

Progressive Disclosure

The body is a clear, well-sectioned overview with exactly one clearly-signaled, one-level-deep reference ('Read references/contract.json for the exact input and output JSON schemas, supported fields, and defaults'), and that file exists in the bundle with precisely that content. This matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

66%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 answers both what and when with an explicit 'Use when' clause and occupies a distinct, low-conflict niche. Its weaknesses are limited action coverage (a single verb) and trigger terms that lean technical/abstract rather than natural user phrasing with synonyms.

Suggestions

Broaden capability coverage with 1-2 more concrete actions, e.g., 'Returns category label, destination, item count, and freshness metadata for a destination category page.'

Add natural trigger phrases and synonyms users would actually say, such as 'Use when asked about a GoVisit destination category page, category listing, or place-type overview.'

DimensionReasoningScore

Specificity

"Read the published overview for the selected destination category page" names the domain and one concrete action, but offers no broader coverage of capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. It is not a 4 because it does not list several distinct specific actions.

3 / 5

Completeness

Both what ("Read the published overview for the selected destination category page") and when ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision") are explicitly present. It falls short of 5 because the when-clause is abstract ('needs this evidence') rather than concrete trigger phrases a user would actually say.

4 / 5

Trigger Term Quality

Phrases like "published overview", "destination category page", "GoVisit evidence", and "integration or travel decision" are relevant, but common natural variations users would say (e.g., "category page", "destination guide", "places overview") are missing. It has some relevant keywords but lacks synonym coverage, fitting anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (GoVisit published category-page overviews over HTTP) with distinct triggers tied to the named tool and site, giving minimal overlap risk with other skills. It clearly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

15

/

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-category-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.