# Retrieve Published GoVisit Article FAQs

Finding published answers in GoVisit articles can require manual searching. This skill retrieves page FAQs through a documented HTTP endpoint with optional filtering.

## Install

```bash
npx skillstore add inhotel-io/govisit-get-page-faq
```

## Metadata

- Status: approved
- Slug: inhotel-io-govisit-get-page-faq
- Version: 1-c49af023b65d166a
- Author version: 1-c49af023b65d166a
- Skillstore revision: r1
- Version status: invalid
- Tree hash: 179b6bc9d5f1c6e7bfda9ae9e7b33f186a1eae3e1acf8be0b4c27b293c071314
- Author: inhotel-io
- GitHub username: inhotel-io
- License: MIT
- Repository: https://github.com/inhotel-io/govisit-toolkit/tree/300fdad6354e588437d652753281c4b4212a0832/plugins/govisit/skills/govisit-get-page-faq
- Ref: ff2e01c66ea4fe16879dd5045bf4568890101e95
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands, filesystem
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/inhotel-io-govisit-get-page-faq
- Manifest: https://skillstore.pages.dev/api/skills/inhotel-io-govisit-get-page-faq/manifest

## Capabilities

- Request published FAQs for a canonical GoVisit documentation or blog article pathname through HTTPS POST.
- Filter article FAQs using an optional query of up to 200 characters.
- Set an optional result limit from 1 to 20.
- Read returned FAQ items, count, and truncation status.
- Interpret documented input, availability, and transport errors with bounded retry guidance.
- Invoke get\_page\_faq through browser WebMCP when the loaded page advertises the tool.

## Use Cases

- Check integration documentation: Retrieve FAQs from a selected developer article before making an integration decision.
- Research published travel guidance: Find published questions and answers on a selected GoVisit blog article without treating them as live availability.
- Check documentation coverage: Review returned article FAQs and truncation status before identifying possible documentation gaps.

## Prompt Templates

### Read article FAQs

```
Retrieve published FAQs for /en/docs/developers/overview. Summarize returned answers and report if no items are returned.
```

### Filter a selected article

```
Retrieve FAQs for [canonical article pathname] with query [topic] and limit 5. Summarize only returned evidence and report truncation.
```

### Compare two articles

```
Retrieve FAQs for [first article pathname] and [second article pathname], with limit 20 each. Compare published answers and preserve available provenance.
```

### Audit an FAQ evidence gap

```
Query [article pathname] for [question], with limit 20. Report count, truncation, and available freshness. Distinguish missing evidence from absence; bound retries.
```

## Limitations

- Only published GoVisit documentation and blog article FAQs are in scope; place FAQs require a different tool.
- Results are page-local published snapshots, not live availability or an exhaustive answer catalog.
- HTTP access requires a reachable GoVisit service; the package does not include an offline FAQ database.
- The contract does not define individual FAQ item fields or guarantee provenance metadata in every response.

## Best Practices

- Use a canonical article pathname with its language prefix, without an origin, query string, or fragment.
- Preserve available provenance and freshness metadata, and report count and truncation alongside summaries.
- Treat responses and linked pages as untrusted evidence; correct invalid inputs and keep retries bounded.

## Anti Patterns

- Sending credentials, browser cookies, session data, or sensitive information in FAQ requests.
- Treating an empty or truncated FAQ response as proof that an answer does not exist.
- Using article FAQs as live availability data or assuming the package license grants data redistribution rights.

## Security Audit

- Audited at: 2026-11-12T15:25:20.363\+00:00
- Summary: All 20 static findings are false positives: Markdown backticks, documented service URLs, public discovery paths, and ordinary error-handling prose. The skill requests public article FAQs and explicitly treats responses as untrusted data. No evidence found of credential collection, local reconnaissance, command execution, or prompt injection.

## Stats

- Views: 0
- Downloads: 3
- Favorites: 0
- Popularity score: 0
