CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

govisit-get-page-faq

Read the published questions and answers on the selected blog or documentation 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/govisit-get-page-faq/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.

The body delivers an executable, well-sequenced single-call procedure with a clean one-level reference into contract.json and thorough error-handling guidance. Its weaknesses are token efficiency — a duplicated intro plus heavy version/digest/licensing boilerplate — and small clarity gaps around truncated results and one ambiguous sentence.

Suggestions

Trim or relocate the 'Source and updates' and 'Licensing' sections (version string, sha256 digests, download URLs) to a bundled file or the contract, and drop the verbatim repeat of the description as the intro.

Clarify the ambiguous sentence 'The HTTP body requires pagePath plus the tool arguments' — pagePath is itself a tool argument — and state plainly that the body is just the tool arguments JSON.

Add a line on handling truncated=true (e.g., re-request with a `limit` up to 20, per the contract) to close the workflow's main feedback-loop gap.

DimensionReasoningScore

Conciseness

The core 'Call the tool' and 'Interpret the response' sections are tight, but the body repeats the frontmatter description verbatim as its intro and carries ~20 lines of package-management boilerplate in 'Source and updates' and 'Licensing' (version string, sha256 digest, download/discovery URLs, data-use license). The rubric's guideline on time-sensitive version information penalizes this, matching 'mostly efficient but includes some unnecessary content that could be tightened'.

3 / 5

Actionability

"Make one HTTPS POST request to `https://govisit.ai/api/tools/v1/get_page_faq` with `Content-Type: application/json`" plus a copy-pasteable JSON body example is directly executable, and per-status-code remediation (400/413/415 correct the request, 429 wait for Retry-After, 503 unavailable) covers the common failure cases. It stops short of a 5 because no full request command or sample response is shown inline and the handling of `truncated`/`limit` is left entirely to contract.json.

4 / 5

Workflow Clarity

As a simple single-call skill, the sequence is unambiguous: build pagePath, POST once, read data.items/count/truncated, and the error section provides explicit corrective feedback loops ('invalid-input means correct the arguments', '429 requires waiting for Retry-After'). Minor gaps remain — the sentence 'The HTTP body requires pagePath plus the tool arguments' is confusing, and no guidance says what to do when truncated is true (e.g., re-request with limit) — so it does not reach 5.

4 / 5

Progressive Disclosure

The single bundle reference is real (references/contract.json exists), one level deep, and well signaled: "Read [references/contract.json](references/contract.json) for the exact input and output JSON schemas, supported fields, and defaults", with schema details correctly kept out of the body. Minor gaps: the reference URL is duplicated inline, and the source/licensing boilerplate lives in SKILL.md rather than a separate file, which keeps it below the cleanly split 5 anchor.

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 concise, in third person, and correctly pairs a clear 'what' with an explicit 'Use when' clause. Its main gaps are trigger-term coverage — the obvious keyword 'FAQ' never appears — and a single-action 'what' that could name more concrete capabilities.

Suggestions

Include the natural trigger terms 'FAQ' and 'frequently asked questions' alongside 'questions and answers', since 'FAQ' is the phrase users would most likely say.

Add one or two more concrete capabilities to the 'what' clause (e.g., returns the published items, count, and truncation status for the page) to lift specificity.

Ground the 'when' clause in more user-shaped triggers, such as 'when the user asks about FAQs or questions on a GoVisit blog or docs page'.

DimensionReasoningScore

Specificity

"Read the published questions and answers on the selected blog or documentation article" names the domain (published Q&A on blog/docs articles) and one concrete action, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions (e.g., what fields are returned or how results are consumed), so it is not a 4.

3 / 5

Completeness

It answers both: 'what' ("Read the published questions and answers on the selected blog or documentation article") and an explicit 'when' ("Use when an agent needs this published GoVisit evidence through HTTP for an integration or travel decision"). The when-clause is explicit but phrased in abstract terms ('evidence', 'integration or travel decision') rather than concrete user trigger phrases, so it falls short of the 5 anchor.

4 / 5

Trigger Term Quality

Relevant keywords are present ("questions and answers", "blog", "documentation article", "GoVisit", "integration or travel decision"), but the most natural trigger term a user would say — "FAQ" or "frequently asked questions" — is absent, as are common variations. This fits 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The GoVisit-specific framing ('published GoVisit evidence through HTTP', blog/documentation articles) carves a clear niche with minimal conflict risk against generic skills. Minor overlap remains with closely related GoVisit page-reading skills (e.g., get_place_section with section faq), which keeps it below a 5.

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