CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-destination-highlights

Read the bounded published highlights shown on the destination page. 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-list-destination-highlights/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a clear, actionable single-task skill: exact endpoint, request body, response interpretation, and thorough error handling, with a real, well-signaled contract reference. Its main cost is token efficiency — repeated qualifications ('bounded', freshness caveats) and provenance/digest detail duplicated from the frontmatter inflate the body without adding guidance.

Suggestions

State the bounded-subset caveat once and drop the repeated 'bounded published highlights' / 'bounded list' / 'bounded subsets' qualifiers to tighten the body.

Move the version string, source digest, and update mechanics out of the body (or into a short pointer to the frontmetadata/index) since they duplicate the frontmatter and are time-sensitive.

Defer the inline error-schema and default-field detail to references/contract.json, keeping only the action per error class, so the reference carries the full contract.

DimensionReasoningScore

Conciseness

The body is mostly efficient — endpoint, argument rules, and error semantics earn their tokens — but the 'bounded' concept is repeated three times ('bounded published highlights', 'bounded list', 'bounded subsets'), and the Source and updates section repeats version and sha256 digest strings already in the frontmatter, which the guidelines penalize as time-sensitive detail outside a deprecation section. This fits anchor 3 ('mostly efficient but could be tightened') rather than anchor 4, which allows only minor trimming.

3 / 5

Actionability

Concrete, executable guidance is given: "Make one HTTPS POST request to https://govisit.ai/api/tools/v1/list_destination_highlights with Content-Type: application/json", a filled-in JSON body example, and per-status error actions (e.g., "429 requires waiting for Retry-After"). It stops short of anchor 5's copy-paste-ready command covering common cases — no ready-to-run curl or equivalent snippet is provided.

4 / 5

Workflow Clarity

The single action is unambiguous (POST a canonical pagePath, read data.items/count), and error recovery is explicit for every completeness value and HTTP status, which serves as the feedback loop. It sits just below anchor 5 because the call/interpret/error flow is spread across interleaved sections with some redundant restatement rather than a crisp sequenced procedure.

4 / 5

Progressive Disclosure

The body is a well-organized overview with headers, and the sole bundle reference (references/contract.json, verified to exist) is clearly signaled one level deep with both a relative link and a canonical URL. It misses anchor 5 because a fair amount of contract detail (error semantics, defaults, field rules) is duplicated inline instead of fully deferred to the reference.

4 / 5

Total

15

/

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 clearly communicates a narrow, distinctive capability with an explicit 'Use when' clause, keeping conflict risk minimal. Its main weaknesses are limited action coverage (one action) and trigger phrasing that leans on internal jargon ('published GoVisit evidence through HTTP') rather than natural user terms.

Suggestions

Enumerate the concrete actions taken with the data (e.g., list highlights, read item counts, check freshness) instead of a single 'read' verb to raise specificity.

Reword the trigger with natural user-facing phrasing (e.g., 'Use when asked about destination highlights, top attractions, or what a GoVisit destination page features') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Read the bounded published highlights shown on the destination page" names a concrete, well-qualified action in a specific domain, but only one action is listed rather than several, matching the '1-2 concrete actions, not comprehensive' anchor. It falls short of anchor 4, which expects several specific actions listed.

3 / 5

Completeness

Both parts are explicit: the 'what' ("Read the bounded published highlights shown on the destination page") and the 'when' ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision"). The trigger clause is present but abstract, so it matches anchor 4 ('when' could be more explicit or specific) rather than anchor 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present ("highlights", "destination page", "GoVisit", "travel decision"), but phrasing like "published GoVisit evidence through HTTP" is jargon-weighted and natural user variations or synonyms are missing. This fits anchor 3 rather than anchor 4's 'good keyword coverage' with only a few gaps.

3 / 5

Distinctiveness Conflict Risk

The description carves out a very narrow niche — reading GoVisit destination-page highlights over HTTP — with no plausible overlap with other skills. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') and is clearly above anchor 4's 'minor overlap risk'.

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-highlights/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.