CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-destination-places

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

Quality

77%

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-destination-places/SKILL.md
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.

The body delivers an executable single-call workflow with clear error recovery and a clean one-level reference structure. Its main weakness is redundancy — repeated pathname/language rules and boilerplate version metadata that could be trimmed.

Suggestions

State the pathname rule (no origin, query, fragment, cache-refresh flag) once — it currently appears in both the prose paragraph and the following bullet.

Trim or collapse the "Source and updates" section: the version digest, canonical URL, and installer policy duplicate frontmatter metadata and do not aid execution.

Add a brief example response snippet (e.g., data.items entry shape) so the interpretation section is concrete rather than deferring entirely to the contract.

DimensionReasoningScore

Conciseness

The body is mostly operational, but the pathname rule and language/scope derivation are each stated twice, and the "Source and updates" section inlines version digests and installer policy that add tokens without aiding execution.

3 / 5

Actionability

Concrete endpoint, method, content-type, a copy-paste JSON body, and per-status-code corrective actions make the request side executable; the response side stays abstract, deferring entirely to the contract.

4 / 5

Workflow Clarity

A simple single-task skill with one unambiguous POST action and explicit error-recovery feedback (invalid-input → correct arguments, 429 → wait for Retry-After, avoid unbounded retries); read-only, so no validation cap applies.

5 / 5

Progressive Disclosure

A well-sectioned ~70-line overview that offloads full schemas to a real one-level-deep reference (references/contract.json) with a clear statement of its contents; navigation is easy.

5 / 5

Total

17

/

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.

A distinct, correctly scoped description with an explicit use-when clause, but it relies on product-specific jargon and thin action coverage. Adding natural synonyms and one or two more concrete capabilities would strengthen it.

Suggestions

Add one or two more concrete actions (e.g., what fields can be filtered or what the response contains) to raise specificity beyond a single action.

Include natural user phrasings like "places to visit", "attractions", or "things to do in a destination" so the trigger terms match what users actually say.

Make the "when" clause more concrete, e.g. "Use when building travel integrations or deciding between destinations and need published place evidence over HTTP."

DimensionReasoningScore

Specificity

"Filter the published place cards already present on the destination page" names the domain and one concrete action, but offers no other actions, filter details, or output shape — not comprehensive.

3 / 5

Completeness

Both a clear "what" (filter published place cards on the destination page) and an explicit "Use when..." clause are present, though the trigger context could be more concrete and natural.

4 / 5

Trigger Term Quality

Terms like "place cards", "destination page", and "GoVisit" are relevant but jargon-leaning; natural user phrasings such as "places to visit" or "things to do" are missing.

3 / 5

Distinctiveness Conflict Risk

"GoVisit", "place cards", and "destination page" carve a clear niche with distinct triggers; overlap risk with other skills is minimal.

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