CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-category-section

Read one published section for the selected destination category 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-get-category-section/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, actionable instruction sheet: exact endpoint and body, precise error-handling semantics, and a clean split of schema detail into a real bundled contract file. Remaining improvement is minor: duplicated path/version details and a response-shape example left entirely to the external contract.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanation of concepts Claude already knows, but has minor trimmable redundancy: 'no origin, query or fragment' is stated twice, and the version, digest, and canonical URL from frontmatter are repeated in the Source and updates section, fitting the efficient-with-minor-overexplanation anchor.

4 / 5

Actionability

Concrete, executable call guidance is provided: the exact endpoint, Content-Type, a request body example, and specific error semantics per status code (400/413/415, 404, 429 with Retry-After, 503); minor gaps remain, such as no inline example of a successful response body, which is delegated entirely to the contract reference.

4 / 5

Workflow Clarity

The call-then-interpret sequence is clear with explicit error-recovery feedback loops ('invalid-input means correct the arguments', '429 requires waiting for Retry-After', '404 requires checking the endpoint version or canonical page path'), but prerequisite steps like resolving a canonical link to pagePath and the HTTP-vs-WebMCP branch are described as scattered bullets rather than a sequenced workflow, leaving minor gaps versus the level 5 anchor.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clear sections (call, interpret, WebMCP, source, licensing) and exactly one clearly signaled, one-level-deep reference (references/contract.json) that exists in the bundle and appropriately holds the full input/output schemas, matching the clear-overview anchor.

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 is a distinct, niche-scoped statement that clearly states what the skill does and includes an explicit use-when clause. Its weaknesses are limited action coverage (a single verb), jargon-leaning trigger phrasing, and a when-clause that describes agent needs rather than concrete user-facing triggers.

Suggestions

List the concrete section types readable (e.g., overview, articles, place lists/counts) so the single 'Read one published section' verb conveys more specific capability coverage.

Add natural trigger phrases users or planners would actually say, such as 'category', 'places', 'hotel', 'things to do', or 'published section', instead of the technical phrase 'published GoVisit evidence through HTTP'.

Make the when-clause more concrete, e.g. 'Use when the user asks about a GoVisit destination category page section or needs published section data for a travel decision', to sharpen trigger matching and distinguish it from sibling GoVisit skills.

DimensionReasoningScore

Specificity

The description names the domain ("selected destination category page") and one concrete action ("Read one published section"), matching the 1-2 concrete actions anchor; it does not list several specific actions, so it does not reach the level 4 anchor.

3 / 5

Completeness

It explicitly answers both what ("Read one published section for the selected destination category page") and when ("Use when an agent needs this published GoVisit evidence... for an integration or travel decision"), but the when-clause lacks concrete user trigger phrases, so it stops short of the level 5 anchor.

4 / 5

Trigger Term Quality

Relevant keywords like "GoVisit", "destination category page", and "travel decision" are present, but phrasing such as "published GoVisit evidence through HTTP" is jargon-heavy and common natural variations or synonyms are missing, fitting the some-relevant-keywords anchor rather than good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The GoVisit destination-category-section niche is clear and mostly distinct, but sibling GoVisit skills fetching similar published page evidence create minor overlap risk with closely related skills, matching the level 4 rather than the minimal-conflict level 5 anchor.

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-get-category-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.