CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-documentation-page

Read bounded structured content from the selected published article. Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision.

Quality

72%

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-get-documentation-page/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a competently built integration skill: the HTTP contract is fully specified, errors have explicit recovery paths, and schema detail is properly delegated to a real one-level reference file. The main drags are token waste from duplicated provenance/version boilerplate and one genuinely ambiguous sentence about request-body composition.

Suggestions

Fix the ambiguous instruction "The HTTP body requires pagePath plus the tool arguments" — state plainly that the body is exactly the tool arguments per the input schema (pagePath required, optional section).

Cut the duplicated version string, sha256 digest, and repeated canonical/contract URLs; move the "Source and updates" and "Licensing" boilerplate into a separate bundled file to reclaim context-window tokens.

Add one complete copy-paste request (e.g., a curl command) and a minimal sample success response to make the common case fully executable without opening contract.json.

DimensionReasoningScore

Conciseness

The core call/interpret sections are dense and mostly earn their tokens, but the body pads with material an agent does not need: the version string and sha256 digest repeated from the frontmatter, the canonical URL and contract URL each stated twice, and a multi-paragraph "Source and updates" section about installer mechanics. Time-sensitive version/digest data appears outside any deprecation context, which the guidelines penalize. This is "mostly efficient but includes some unnecessary explanation" (anchor 3), not severely padded (anchor 2) since the operational guidance itself is tight.

3 / 5

Actionability

The instruction is concretely executable: exact endpoint, method, Content-Type, a copy-paste JSON body example, and per-status-code recovery actions ("429 requires waiting for `Retry-After`"). It falls short of anchor 5 because no complete request command (e.g., a curl line) or sample success/error response body is shown — the reader must assemble the request from pieces and consult contract.json for output shape. It is well above anchor 3 since everything given is real and executable, not pseudocode.

4 / 5

Workflow Clarity

The sequence is clear — construct a canonical pagePath, POST once, interpret data via the output schema, then branch on explicit error signals with recovery actions (correct arguments on invalid-input, check path on 404, honor Retry-After, avoid unbounded retries). For this simple read-only skill that alone approaches a 5, but one sentence creates real ambiguity: "The HTTP body requires pagePath plus the tool arguments" is confusing because pagePath *is* a tool argument and the contract's inputSchema admits only pagePath and section. That gap in the single most critical instruction (what exactly goes in the body) holds it at anchor 4 ("minor validation gaps" / minor ambiguity) rather than 5.

4 / 5

Progressive Disclosure

The bundle is well structured: operational guidance lives in SKILL.md while exact schemas are correctly split into references/contract.json, which is real, referenced with a clear markdown link, and its purpose is described ("exact input and output JSON schemas, supported fields, and defaults") — a well-signaled, one-level-deep reference. It does not reach anchor 5 because the body also inlines package-management boilerplate ("Source and updates", "Licensing", repeated digests/URLs) that is not navigational or operational content, a minor organization gap characteristic of anchor 4.

4 / 5

Total

15

/

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 structurally sound — third-person voice, a stated action, and an explicit 'Use when...' clause — so it clears the completeness floor. Its weaknesses are vocabulary and coverage: it leads with internal jargon ("bounded structured content", "published GoVisit evidence") instead of natural trigger words like "documentation" or "docs", and it describes only one action.

Suggestions

Rewrite the 'what' to name the concrete operation and outputs, e.g. "Fetch a published GoVisit documentation page (content, headings, sections) as structured JSON over HTTPS."

Replace jargon triggers with natural user phrasing: mention "documentation", "docs page", and "GoVisit" in the 'Use when' clause instead of "this published GoVisit evidence".

State the transport explicitly and simply ("via a single HTTPS POST") rather than "through HTTP", which reads as a qualifier rather than a capability.

DimensionReasoningScore

Specificity

"Read bounded structured content from the selected published article" names the domain (published GoVisit article) and one concrete action (reading bounded structured content), but coverage is not comprehensive — no mention of sections, headings, truncation handling, or the HTTP mechanics that the body actually performs. It matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") rather than 4, which requires several specific listed actions.

3 / 5

Completeness

Both parts are present: the "what" ("Read bounded structured content from the selected published article") and an explicit "when" clause ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision"). It falls short of anchor 5 because the trigger phrases are not concrete user-natural terms — "this published GoVisit evidence" is opaque — leaving the 'when' specific but unnatural; the 'Use when...' clause is explicit, so it is above anchor 3.

4 / 5

Trigger Term Quality

Keywords present are "published article", "GoVisit", "HTTP", "integration", "travel decision" — the natural phrases a user would actually say ("documentation", "docs", "get the documentation page") are absent, and "published GoVisit evidence" is internal jargon rather than user vocabulary. This lands at anchor 3 ("Some relevant keywords but missing common variations or synonyms"); it is above anchor 2 because GoVisit and article are domain-relevant, not purely generic.

3 / 5

Distinctiveness Conflict Risk

The GoVisit/HTTP/travel-decision framing carves out a clear niche that is unlikely to fire for unrelated skills, satisfying most of anchor 5. However the opening action "Read bounded structured content from the selected published article" is generic enough to overlap with any documentation-reading skill before the niche qualifiers kick in, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills").

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