CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-destination-activities

Read the bounded published activities shown 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-activities/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.

A well-structured, highly actionable single-purpose skill: the HTTP call, response interpretation, and error recovery are concrete and unambiguous, and the contract reference is properly separated one level deep. The main weakness is redundancy — the Source and updates section duplicates frontmatter metadata (version, digest, canonical URL) and the contract link repeats its hosted URL.

Suggestions

Trim the Source and updates section: drop the version string, source digest, and canonical URL that already appear in the frontmatter metadata, keeping only the package/discovery links and the update guidance.

Remove the inline raw GitHub URL for contract.json, keeping just the relative link (or just the hosted URL) to avoid stating the same reference twice.

Add one complete runnable request example (e.g., a curl command with headers and body) to make the call guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The operational sections (Call the tool, Interpret the response) are dense and efficient, but "Source and updates" restates the version (`1-c49af023b65d166a`), source digest, and canonical URL already in the frontmatter metadata, and the contract reference repeats the raw GitHub URL alongside the relative link — matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

The body gives an exact endpoint, method, Content-Type, a concrete JSON body example, and per-status error handling (400/413/415 correct the request, 429 wait for `Retry-After`, 503 temporary), which is mostly executable guidance. It falls short of copy-paste ready only in lacking a complete runnable request example (e.g., a curl command).

4 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: one HTTPS POST with the given body, then read data.items/data.count, with an explicit error-recovery mapping (invalid-input means correct arguments, unavailable means not served, avoid unbounded retries). The simple-skill exception applies and the error feedback loop is explicit.

5 / 5

Progressive Disclosure

The bundle reference references/contract.json exists, is exactly one level deep, and is clearly signaled with its purpose ('exact input and output JSON schemas, supported fields, and defaults') — keeping schemas out of SKILL.md. Body sections (Call the tool, Interpret the response, Browser WebMCP, Source and updates, Licensing) are well-organized and easy to navigate.

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, honest description that explicitly states both what the skill does and when to use it, though the action coverage is thin (a single 'read' action) and the trigger language leans technical rather than natural. Tightening the when-clause into concrete user-facing trigger phrases would lift it further.

Suggestions

Enumerate the concrete capabilities rather than one 'read' action, e.g. 'List the activities published on a GoVisit destination page, returning each item's fields plus count, freshness, and canonical page URL.'

Add natural trigger phrases users would actually say, such as 'things to do', 'activities', or 'attractions for a destination', alongside the current technical terms.

Make the when-clause more concrete, e.g. 'Use when the user asks about activities or things to do in a destination, or when an integration needs GoVisit's published activity data.'

DimensionReasoningScore

Specificity

"Read the bounded published activities shown on the destination page" names the domain (GoVisit destination activities) and one concrete action, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not list several specific actions (anchor 4), and is well above the generic-only anchors.

3 / 5

Completeness

Both parts are explicit: the what ("Read the bounded published activities 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 when-clause is present but somewhat abstract rather than concrete trigger phrases, so it sits at 'Has both what and when; when could be more explicit or specific' rather than 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ("published activities", "destination page", "GoVisit", "integration", "travel decision") but phrasing like "bounded", "published GoVisit evidence through HTTP" is technical rather than the natural phrases a user would say, and common synonyms are missing — matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — GoVisit's published destination activities over HTTP — with distinct triggers ("GoVisit", "destination page", "published activities") that are unlikely to fire for unrelated skills, matching 'Clear niche with distinct triggers; minimal conflict 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-activities/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.