CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-list-related-places

Find bounded, page-local related place cards using optional published-field filters. 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-related-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 well-structured, actionable overview for a single HTTP tool call, with clean one-level-deep disclosure into the bundled contract and thorough error-recovery guidance. Its main weakness is token overhead from the duplicated description line and the versioning/licensing boilerplate that adds nothing to execution.

Suggestions

Drop the verbatim repeat of the frontmatter description under the H1 and let the heading stand on its own.

Condense the "Source and updates" section to the canonical URL and a one-line update instruction, moving the digest and installer details out of the operational body.

Add a single complete copy-paste request example (e.g., a curl command with headers and body) to close the last actionability gap.

DimensionReasoningScore

Conciseness

The core call-and-interpret guidance is tight, but the frontmatter description is repeated verbatim under the H1, and the "Source and updates" and "Licensing" sections carry version digests, installer boilerplate, and license URLs that are non-operational for executing the task. This is mostly efficient with noticeable tightening opportunities rather than only minor trims.

3 / 5

Actionability

The body gives a concrete endpoint, method, content type, and a copyable JSON body ("Make one HTTPS POST request to `https://govisit.ai/api/tools/v1/list_related_places`..."), plus specific per-status error handling. It stops just short of fully copy-paste-ready commands (no complete curl/http example), which is what the top anchor requires.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action is unambiguous: a single HTTPS POST with pagePath and tool arguments. The error section supplies explicit feedback loops ("`invalid-input` means correct the arguments", "429 requires waiting for `Retry-After`", "Avoid unbounded retries"), so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The body is a clear overview with one well-signaled, one-level-deep reference: "Read [references/contract.json](references/contract.json) for the exact input and output JSON schemas, supported fields, and defaults." That file exists in the bundle and contains exactly those schemas, so navigation is clean and appropriately split.

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 niche capability with an explicit use-when clause, but it is written in dense technical jargon that limits natural trigger coverage and makes the when-condition harder to match in practice. It is serviceable and distinct, just not user-phrased.

Suggestions

Rewrite the trigger clause around natural user phrasings, e.g. "Use when the user asks about nearby, similar, or related places on a GoVisit page".

Add one or two concrete action verbs beyond "find" (e.g. "list and filter related place cards by category, audience, or neighborhood") to raise specificity.

Trim qualifier stacking like "bounded, page-local" and "published-field filters" to one plain-language phrase so the description reads less like internal jargon.

DimensionReasoningScore

Specificity

"Find bounded, page-local related place cards using optional published-field filters" names the domain and a single concrete action with qualifiers, but does not list several specific actions, matching the 1-2 concrete actions anchor rather than the several-actions anchor above.

3 / 5

Completeness

Both parts are present: what = "Find bounded, page-local related place cards..." and when = "Use when an agent needs this published GoVisit evidence... for an integration or travel decision". The when clause is explicit but convoluted and conditional, so it does not reach the clear, concrete-trigger-phrases level.

4 / 5

Trigger Term Quality

Terms like "related places", "GoVisit", and "travel" are relevant, but natural user phrasings such as "nearby places" or "similar places" are missing and much of the wording is technical ("bounded, page-local", "published-field filters", "through HTTP"), fitting the some-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

The "GoVisit" platform name and the specific related-places function carve out a clear niche, but "for an integration or travel decision" is broad enough for minor overlap with sibling GoVisit place tools or general travel skills, keeping it just below the minimal-conflict 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-list-related-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.