CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-collection-section

Read one published section for the selected destination collection 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-get-collection-section/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 instruction body for a single HTTP tool call, with excellent error-handling guidance and proper use of a one-level bundle reference. The main cost is token weight from administrative sections (source/version/licensing) and a redundant restatement of the description.

DimensionReasoningScore

Conciseness

The core sections ('Call the tool', 'Interpret the response') are dense and directive, but the body opens by repeating the frontmatter description verbatim and the 'Source and updates' and 'Licensing' sections spend ~20 lines on administrative details (version digests, installer mechanics, data-use licensing) that do not help execute the call. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the redundancy and administrative padding are more than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: exact endpoint and method ('HTTPS POST to https://govisit.ai/api/tools/v1/get_collection_section with Content-Type: application/json'), a copy-paste JSON body, rules for constructing pagePath, and per-status-code remediation (429 → wait for Retry-After, 400/413/415 → correct the request). It stops short of 5 because no complete request example (e.g., a curl command) is given, leaving the agent to assemble method, headers, and body itself.

4 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: construct pagePath from a canonical link, pick a supported section, POST, then interpret via the output schema. Error feedback loops are explicit ('invalid-input means correct the arguments', 'Avoid unbounded retries', Retry-After handling), so the simple-skill exception applies and the content matches the top anchor.

5 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep references — 'Read references/contract.json for the exact input and output JSON schemas, supported fields, and defaults' — and the referenced file exists in the bundle (verified). Schemas and detailed contract semantics are correctly split into the reference while the body keeps only decision-relevant guidance, matching the top anchor.

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 concise, third-person description with an explicit 'Use when' clause and a highly distinctive niche. Its main weaknesses are limited action coverage (a single verb) and trigger terms that lean on product jargon (GoVisit, HTTP) rather than natural user phrasing.

Suggestions

Broaden specificity by naming what the tool returns (e.g., 'returns overview fields, article content, or items/count for the section'), not just the single 'read' action.

Add natural trigger phrases to the 'when' clause, such as 'when the user asks about a GoVisit destination collection page or needs published section content'.

Consider mentioning related sections or the sibling tools' scope boundaries so agents can distinguish this skill from neighboring GoVisit section-reading skills.

DimensionReasoningScore

Specificity

The description names the domain and a single concrete action — "Read one published section for the selected destination collection page" — which matches the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because only one action is listed (no mention of what is returned or how results are used beyond 'read'), and not a 2 because the action is genuinely concrete rather than generic.

3 / 5

Completeness

Both parts are explicit: the 'what' ("Read one published section for the selected destination collection page") and the 'when' ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision"), matching the anchor for both present with room for more specificity. It is not 5 because the 'when' clause is fairly abstract — 'needs this published GoVisit evidence' — rather than concrete trigger phrases users would say.

4 / 5

Trigger Term Quality

Relevant domain keywords are present ("published section", "destination collection page", "GoVisit", "HTTP", "integration or travel decision") but they are product-specific terms rather than the natural phrases or synonyms a user would broadly say, fitting the anchor 'some relevant keywords but missing common variations or synonyms'. It falls short of 4 because there are no natural trigger variations a user might utter when needing published destination-collection evidence.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — reading one published section of a GoVisit destination collection page over HTTP — with distinct, product-specific triggers, so the risk of firing for an unrelated skill is minimal. It clearly matches the 'clear niche with distinct triggers' anchor.

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-get-collection-section/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.