CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-category-overview

Read the published overview for the selected destination category page. Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/govisit-get-category-overview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 body is a well-structured, highly actionable guide for a single HTTP tool call, with a clean one-level reference to the contract and thorough error-handling guidance. Its main weaknesses are redundancy (repeated description and pagePath rules, version/digest detail) and one confusing sentence about the request body.

Suggestions

Remove the verbatim repetition of the description in the opening paragraph and consolidate the pagePath rules into a single statement to tighten token usage.

Clarify or delete 'The HTTP body requires pagePath plus the tool arguments' — per the contract, pagePath is the only argument — and consider adding one complete copy-paste request example (e.g., curl with headers and body).

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening paragraph repeats the frontmatter description verbatim, the pagePath rules are stated twice ('Use a canonical GoVisit pathname with no origin, query or fragment' then 'do not send an origin, query, fragment or cache-refresh flag'), and version digests ('sha256:c49af...') add time-sensitive tokens outside any deprecated/old-patterns section.

3 / 5

Actionability

Gives concrete executable guidance — the exact endpoint ('https://govisit.ai/api/tools/v1/get_category_overview'), content type, a JSON body example, and per-status error handling ('429 requires waiting for Retry-After') — but there is no complete copy-paste request example (e.g., a curl command) covering the common case.

4 / 5

Workflow Clarity

The single call is unambiguous with explicit error-recovery feedback ('invalid-input means correct the arguments', 'unavailable means the requested operation or context could not be served'), but the sentence 'The HTTP body requires pagePath plus the tool arguments' is confusing since pagePath is the only input argument, leaving a minor clarity gap.

4 / 5

Progressive Disclosure

A clear, well-sectioned overview with one well-signaled, one-level-deep reference ('Read references/contract.json for the exact input and output JSON schemas' — verified to exist and contain those schemas), keeping schema bulk out of the body with easy navigation.

5 / 5

Total

16

/

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 and includes an explicit 'Use when' trigger, but it names only a single action and leans on technical phrasing ('published GoVisit evidence through HTTP') rather than natural trigger terms. It is solid but not comprehensive.

Suggestions

Add one or two more concrete capabilities (e.g., what fields the overview returns or what decisions it supports) to raise specificity beyond a single action.

Replace technical phrasing like 'needs this published GoVisit evidence through HTTP' with natural trigger terms a user would say, such as 'Use when the user asks about a GoVisit destination category page or needs its overview for a travel plan or integration'.

DimensionReasoningScore

Specificity

Names one concrete action — 'Read the published overview for the selected destination category page' — with a clear domain, but lists no further actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Both parts are explicit: 'what' ('Read the published overview for the selected destination category page') and 'when' ('Use when an agent needs... for an integration or travel decision'), but the trigger clause is abstract rather than concrete user-mentionable phrases, so it falls short of the 5 anchor.

4 / 5

Trigger Term Quality

Relevant keywords exist ('published overview', 'destination category page', 'GoVisit', 'travel decision'), but 'needs this published GoVisit evidence through HTTP for an integration' is technical phrasing that misses the natural variations a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The GoVisit-specific niche ('published GoVisit evidence', 'destination category page', 'through HTTP') is clearly distinguishable from generic skills with minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

davepoon/buildwithclaude

Path

plugins/all-skills/skills/govisit-get-category-overview/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.