CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-search-documentation

Search the published documentation links rendered on the selected documentation index 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/govisit-search-documentation/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 well-structured, actionable overview: the HTTP call is fully specified, errors map to concrete next steps, and detail is appropriately deferred to the bundled contract. Its main weakness is redundancy — the description, canonical URL, version, and digest are each stated twice — which costs tokens without adding guidance.

DimensionReasoningScore

Conciseness

The body is dense and free of explanations Claude already knows, but repeats the description verbatim under the title and restates the canonical URL, version, and source digest already present in the frontmatter, so it could be tightened.

3 / 5

Actionability

Provides the concrete endpoint, method, content type, a complete example JSON body, and an error-code-to-action mapping, plus a verified pointer to references/contract.json; minor gaps remain (no full request command or example response).

4 / 5

Workflow Clarity

A single-action skill with an unambiguous call instruction ("Make one HTTPS POST request to ... Send the tool arguments directly as the JSON body") and explicit error-recovery guidance (invalid-input means correct arguments, 429 requires Retry-After, avoid unbounded retries).

5 / 5

Progressive Disclosure

The body is a well-sectioned overview that clearly signals the single one-level-deep reference (references/contract.json, verified present) with its purpose, keeping schemas out of the main file.

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 clearly states a single scoped capability and includes an explicit use-when clause, making it distinguishable via the GoVisit brand. However, it describes only one action, leans on jargon-like trigger phrasing ("published GoVisit evidence through HTTP"), and lacks natural trigger terms a user would actually say.

Suggestions

List the concrete capability set more fully (e.g., match documentation titles and paths, return link items and counts) instead of a single action sentence.

Replace jargon triggers like "published GoVisit evidence through HTTP" with natural phrases users would say, such as "search GoVisit docs" or "find documentation links".

Make the "when" clause concrete: name the triggering situations (building a GoVisit integration, deciding on travel options) rather than the abstract "integration or travel decision".

DimensionReasoningScore

Specificity

Names one concrete, well-scoped action ("Search the published documentation links rendered on the selected documentation index page") but lists no additional capabilities, so coverage is not comprehensive.

3 / 5

Completeness

Both "what" (search published documentation links on the index page) and an explicit "Use when" clause are present, but the "when" trigger ("for an integration or travel decision") is abstract rather than a concrete trigger phrase.

4 / 5

Trigger Term Quality

"documentation" and the brand term "GoVisit" are relevant keywords, but "published GoVisit evidence through HTTP" is jargon and common natural variations ("docs", "find documentation") are missing.

3 / 5

Distinctiveness Conflict Risk

The GoVisit brand scoping gives it a clear niche with minimal conflict against unrelated skills, but it overlaps with closely related GoVisit skills such as get_documentation_page.

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-search-documentation/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.