CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-collection-places

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

Quality

76%

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-collection-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 content is a lean, highly actionable single-call skill: an exact endpoint with a ready request body, per-status-code error recovery, and a clean split of schema detail into a real one-level reference. Its main weakness is redundancy — the pagePath rules, no-SSE point, and package metadata are each stated twice, which could be tightened without losing information.

Suggestions

State the pagePath construction rules once (the prose paragraph and the first bullet say the same thing) and drop the duplicated intro line that repeats the frontmatter description verbatim.

Trim the 'Source and updates' section by not restating the version hash and source digest already present in the frontmatter, keeping just the canonical URL and update instruction.

DimensionReasoningScore

Conciseness

The body is dense and directive with no beginner-concept explanations, but contains several duplications: the frontmatter description is repeated verbatim as the intro, the pagePath constraints appear both as prose ("The HTTP body requires pagePath... no origin, query or fragment") and again as a bullet ("do not send an origin, query, fragment or cache-refresh flag"), the no-SSE point is made twice, and the version, digest, and canonical URL are restated from the frontmatter. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' — above 2 because there is no padding or taught concepts, below 4 because the redundancy is real and trimmable.

3 / 5

Actionability

The call is fully specified — "one HTTPS POST request to https://govisit.ai/api/tools/v1/list_collection_places with Content-Type: application/json" plus a copy-paste JSON body with concrete values — and error handling maps each status to an action ("HTTP 400/413/415 require correcting the request; 429 requires waiting for Retry-After"). Minor gaps keep it at 4: no literal executable command (e.g., curl) and no sample response payload, with output shape deferred to contract.json.

4 / 5

Workflow Clarity

This is a simple single-call skill whose single action is unambiguous (construct pagePath → POST → read data.items/data.count), which per the simple-skill exception can score 5. It additionally includes explicit error-recovery feedback loops: "invalid-input means correct the arguments", 429 → wait for Retry-After, and "Avoid unbounded retries", satisfying the 5 anchor's error-recovery requirement rather than the 4 anchor's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview (call, interpret, browser variant, updates, licensing) that delegates the detailed input/output schemas to a clearly signaled, one-level-deep reference: "Read [references/contract.json](references/contract.json) for the exact input and output JSON schemas, supported fields, and defaults" — the file exists and itself contains no further references. Content is appropriately split with easy navigation, matching the 5 anchor; the inline GitHub URL duplicate is a trivial blemish, not an organization gap.

5 / 5

Total

17

/

20

Passed

Description

62%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 cleanly states one concrete capability and includes an explicit 'Use when' clause, keeping a clear niche. Its weaknesses are limited action coverage, an abstract trigger clause phrased around 'evidence' and 'integration or travel decision' rather than natural user language, and missing common synonyms that would improve triggering.

Suggestions

Enumerate the concrete actions the tool supports, e.g., 'List and filter published place cards on a GoVisit destination collection page by category, audience, accessibility, or neighborhood'.

Rewrite the 'Use when' clause around natural trigger phrases, e.g., 'Use when the user wants the places, attractions, or things to do from a specific GoVisit collection page'.

Add common synonyms such as 'list places', 'attractions', or 'things to do' so the description matches how users actually phrase the request.

DimensionReasoningScore

Specificity

"Filter the published place cards shown on the selected destination collection page" names the domain and one concrete action, but no additional actions (e.g., listing, filtering by category, pagination) are enumerated. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4, since several specific actions are not listed; not 2, since the action is concrete rather than generic.

3 / 5

Completeness

Both parts are explicit: the 'what' is "Filter the published place cards shown on the selected destination collection page" and the 'when' is "Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision". The 'when' clause is present but abstract — lacking concrete trigger phrases users would actually say — matching 'Has both what and when; when could be more explicit or specific' rather than the 5 anchor.

4 / 5

Trigger Term Quality

Relevant terms like "place cards", "destination collection page", "GoVisit", and "travel decision" are present, but natural variations a user would say ("list places", "attractions", "things to do") are missing, and "published GoVisit evidence" is jargon rather than a natural phrase. It sits at 'Some relevant keywords but missing common variations or synonyms' — below 4 because keyword coverage is narrow, above 2 because the included terms are domain-relevant rather than generic.

3 / 5

Distinctiveness Conflict Risk

The GoVisit destination-collection niche is clear and unlikely to trigger unrelated skills, but "place cards" and "collection page" overlap with closely related sibling tools in the same GoVisit toolkit (e.g., other list_* page-type tools). This fits 'Mostly distinct; minor overlap risk with closely related skills' — the 5 anchor requires fully distinct triggers with minimal conflict risk.

4 / 5

Total

14

/

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