CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-category-places

Filter the published place cards shown on the selected destination category page. Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision.

Quality

80%

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-list-category-places/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 operational core of this skill is excellent: an exact endpoint, a copy-paste-ready request body, precise argument rules, and specific error-recovery guidance, with schemas properly deferred to a real one-level-deep reference file. The main weakness is the tail of the file, where the 'Source and updates' and 'Licensing' sections spend ~15 lines on installer/maintainer administration and repeat version/digest values already present in the frontmatter.

DimensionReasoningScore

Conciseness

The core sections ('Call the tool', 'Interpret the response') are lean and operational, but 'Source and updates' and 'Licensing' add roughly 15 lines of administrative content (canonical URL, source digest, installer guidance, data license) that does not help execute the task, and the version/digest values are repeated from the frontmatter. Per the guidelines, time-sensitive version info outside a deprecated/old-patterns section further penalizes conciseness.

3 / 5

Actionability

The body gives an exact endpoint ('https://govisit.ai/api/tools/v1/list_category_places'), the required Content-Type, a copy-paste-ready JSON body example, a clearly signaled contract file for full schemas, and specific per-error guidance ('invalid-input means correct the arguments', '429 requires waiting for Retry-After', '404 requires checking the endpoint version or canonical page path'). This is fully executable and covers the common case.

5 / 5

Workflow Clarity

This is a simple, single-action skill and the single action (one HTTPS POST with the tool arguments as the JSON body) is unambiguous, satisfying the simple-skill exception. The interpret/error section adds explicit feedback loops: correct arguments on invalid-input, wait for Retry-After on 429, check endpoint version or page path on 404, and avoid unbounded retries.

5 / 5

Progressive Disclosure

The SKILL.md is a well-sectioned overview, and the one heavy detail (exact input/output JSON schemas, supported fields, defaults) is appropriately split into references/contract.json, which exists in the bundle and is referenced one level deep via a clear markdown link with a description of its contents. Navigation is easy with no inlined bulk reference material.

5 / 5

Total

18

/

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 is well-formed: third-person voice, a concrete what, an explicit 'Use when...' clause, and a clearly staked-out niche that minimizes conflict risk. Its weakness is trigger phrasing — it uses provider jargon ('published GoVisit evidence') and omits the natural terms and place types a user would say when needing this skill, which caps trigger quality and specificity.

Suggestions

Add concrete trigger phrasing to the 'when' clause, e.g. 'Use when the user asks for GoVisit places, hotels, restaurants, or things to do on a destination category page' — this would lift both completeness and trigger_term_quality toward 5.

Include natural synonyms users would say ('places to stay', 'list places', 'points of interest') alongside 'place cards' so the description matches real user phrasing instead of provider jargon like 'published GoVisit evidence'.

Name one or two additional concrete capabilities (e.g. 'filter by name or category and read published items and counts') so the what clause lists several specific actions rather than a single one.

DimensionReasoningScore

Specificity

'Filter the published place cards shown on the selected destination category page' names the domain and one concrete action, but the description lists only a single capability rather than several specific actions. It is below anchor 4 ('lists several specific actions') yet above anchor 2 because the named action is concrete and domain-specific rather than generic.

3 / 5

Completeness

Both parts are present: the what ('Filter the published place cards shown on the selected destination category page') and an explicit when ('Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision'). It falls short of anchor 5 because the when clause is abstract and lacks concrete trigger phrases a user would say, but the explicit 'Use when...' clause keeps it above anchor 3.

4 / 5

Trigger Term Quality

Relevant domain terms are present ('place cards', 'destination category page', 'GoVisit', 'integration or travel decision'), but common natural variations a user would actually say are missing, such as 'list places', 'places to stay', or concrete place types like hotels or restaurants. 'Published GoVisit evidence' is provider jargon rather than user phrasing, keeping it below anchor 4.

3 / 5

Distinctiveness Conflict Risk

'Filter the published place cards shown on the selected destination category page' plus the named GoVisit brand and HTTP delivery defines a clear niche with distinct triggers, so the risk of firing for the wrong skill is minimal even among closely related skills.

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