CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-place-section

Read one published section of the selected place, including spatial details when requested. Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision.

Quality

79%

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-place-section/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 strong example of an API-tool skill: fully executable call spec, comprehensive error-handling guidance, and clean one-level-deep disclosure into a real contract.json reference. Its only meaningful weakness is redundancy — the pagePath rules are stated twice and the update/version metadata duplicates the frontmatter.

Suggestions

Merge the pagePath paragraph and its first bullet into a single statement of the rule to remove the near-verbatim duplication ('no origin, query or fragment' appears in both).

Trim the 'Source and updates' section: the version and sha256 digest already appear in the frontmatter, so the body only needs the canonical URL and a one-line update instruction.

Consider consolidating the four administrative URLs (canonical, package, index, data-use license) into a short two-line list to reduce token cost without losing the update-integrity guidance.

DimensionReasoningScore

Conciseness

The body is mostly tight and prescriptive with no padding about concepts Claude already knows, but it has clear tightening targets: the pagePath rules are stated twice (the 'Use a canonical GoVisit pathname with no origin, query or fragment' paragraph, then again nearly verbatim in the first bullet: 'do not send an origin, query, fragment or cache-refresh flag'), and the 'Source and updates' section repeats the version and source-digest already in the frontmatter along with four administrative URLs. This matches 'mostly efficient but could be tightened' rather than the minor-trim profile of a 4.

3 / 5

Actionability

The guidance is fully executable: an exact endpoint ('https://govisit.ai/api/tools/v1/get_place_section'), required Content-Type, a copy-paste-ready JSON body, section-selection rules, and a complete error-response playbook ('invalid-input means correct the arguments', '429 requires waiting for Retry-After', '503 means temporarily unavailable', 'Avoid unbounded retries'). Nothing remains pseudocode-level; the common case is covered end to end.

5 / 5

Workflow Clarity

This is a simple single-call skill and the single action is unambiguous: one HTTPS POST with the documented body, followed by schema-driven interpretation with explicit per-error remediation steps (correct arguments on invalid-input, wait on Retry-After, check path/endpoint version on 404). The rubric's simple-skill exception applies, and the error mapping even supplies a lightweight validate-and-correct feedback loop; it is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The body is a clear overview with well-organized sections (call, interpret, browser variant, source, licensing) and exactly one one-level-deep reference — [references/contract.json](references/contract.json), verified to exist in the bundle — clearly signaled with a description of what it contains ('exact input and output JSON schemas, supported fields, and defaults'). Schemas are kept out of SKILL.md and delegated to that reference, matching the top anchor.

5 / 5

Total

18

/

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 well-formed with an explicit 'Use when...' clause and a distinctive, branded niche. Its main weaknesses are limited enumeration of concrete capabilities and trigger phrasing that is more technical jargon ('published GoVisit evidence through HTTP') than natural user language.

Suggestions

Enumerate the concrete sections/capabilities available (e.g., location, accessibility, opening hours, FAQ) so the 'what' lists several specific actions rather than one.

Rewrite the trigger clause around natural user phrases such as 'use when the user asks for a place's location details, accessibility evidence, or FAQ' instead of agent-intent jargon like 'published GoVisit evidence through HTTP'.

Add common synonyms users would say (place info, spatial details, accessibility) to broaden natural keyword coverage without adding length.

DimensionReasoningScore

Specificity

The description names the domain ("published section of the selected place") and one to two concrete actions ("Read one published section... including spatial details when requested"), but does not enumerate several specific capabilities the way a score-4 anchor expects. It is more concrete than the 'minimal or generic actions' of a 2, yet not comprehensive enough for a 4.

3 / 5

Completeness

Both parts are explicitly present: 'what' is "Read one published section of the selected place, including spatial details when requested" and 'when' is the explicit "Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision." It falls short of a 5 because the 'when' clause lacks concrete user-side trigger phrases, relying instead on agent-intent language.

4 / 5

Trigger Term Quality

Some relevant natural terms appear ("place", "section", "spatial details", "travel decision"), but the trigger phrasing leans technical ("this published GoVisit evidence through HTTP") and misses common variations or synonyms a user would naturally say (e.g., location details, accessibility, place info). This sits at 'some relevant keywords but missing common variations', not the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The GoVisit branding and the narrow operation (reading one published place section over HTTP) give it a clear niche with minimal conflict against unrelated skills. It stops short of a 5 because closely related sibling skills in the same GoVisit toolkit (e.g., place search or other section-level tools) could plausibly overlap on triggers like 'place' or 'travel'.

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-place-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.