CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-statistics

Use when an agent needs exact GoVisit catalog coverage counts for the physical World or a selected Destination, with observation dates and provenance.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 delivers fully executable call guidance with concrete request bodies and an unusually thorough error-handling map, organized into clear sections with a real, well-described one-level-deep reference. The main gaps are redundancy with the frontmatter metadata and inline licensing/update prose that slightly dilute both conciseness and the overview structure.

Suggestions

Trim the "Source and updates" section: the version, source digest, and canonical URL are already in the frontmatter, so stating them once in the body (or only in the frontmatter) would remove duplicated tokens.

Condense or relocate the "Licensing" section to a short pointer (e.g., a LICENSE file reference), keeping the SKILL.md body focused on calling and interpreting the tool.

DimensionReasoningScore

Conciseness

The body is dense with domain facts Claude would not know (error semantics, metric fields, rounding rules) and pads nothing with basic concepts. However, "Source and updates" repeats the version, source digest, and canonical URL already in the frontmatter, and the description is restated verbatim, so minor trimming remains — anchor 4 rather than 5.

4 / 5

Actionability

"Make one HTTPS POST request to `https://govisit.ai/api/tools/v1/get_statistics` with `Content-Type: application/json`" plus two copy-paste-ready JSON bodies (World/coverage and a Destination pagePath) is fully executable and covers the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The single call-then-interpret sequence is unambiguous, with explicit error-recovery checkpoints: "`invalid-input` means correct the arguments", "429 requires waiting for `Retry-After`", "Avoid unbounded retries". The operation is read-only, so the destructive/batch validation cap does not apply, and the simple-skill exception holds.

5 / 5

Progressive Disclosure

The sole bundle file, references/contract.json, exists and is clearly signaled one level deep ("exact input and output JSON schemas, supported fields, and defaults"), and sections are well organized. Sizable inline non-operational material (licensing, update policy, duplicated URLs) keeps it below anchor 5's clean overview.

4 / 5

Total

18

/

20

Passed

Description

87%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.

A tightly written, third-person description that explicitly covers both what is delivered and when to use it, with concrete GoVisit-specific trigger terms. Its only weaknesses are the single-action scope inherent to the tool and a few missing natural synonyms such as "statistics" or "totals".

DimensionReasoningScore

Specificity

"exact GoVisit catalog coverage counts for the physical World or a selected Destination, with observation dates and provenance" names concrete deliverables and both scopes. It stops short of anchor 5's multiple distinct actions (a single retrieval action) but exceeds anchor 3 because the action's outputs and scopes are fully specified.

4 / 5

Completeness

"Use when an agent needs exact GoVisit catalog coverage counts... with observation dates and provenance" explicitly answers both when (concrete trigger conditions) and what (the returned data). This is stronger than anchor 4, whose 'when' is only generic.

5 / 5

Trigger Term Quality

Natural terms a user would say are present: "coverage counts", "GoVisit", "Destination", "World". It stays below anchor 5 because common synonyms such as "statistics", "totals", or "how many" are absent.

4 / 5

Distinctiveness Conflict Risk

The GoVisit-specific niche ("GoVisit catalog coverage counts", "physical World or a selected Destination") provides distinct triggers with minimal conflict risk against any generic skill, matching anchor 5.

5 / 5

Total

18

/

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-statistics/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.