rollinggo-searchhotel

Hotel search and pricing via the RollingGo CLI. Use when the user wants to search hotels by destination, filter by date/star/budget/tags/distance, inspect ho...

Security Scan

The skill's declared purpose (hotel search via the RollingGo CLI) matches its requirements and instructions; the only notable risk is that the runtime defaults to executing the latest remote package (npx/uvx), which is a supply‑chain/runtime update consideration rather than a functional mismatch.

Purpose & Capability

Name/description, required binaries (rollinggo/npx/node/uvx/uv) and the single required env var (RollingGo_API_KEY) are consistent with a CLI wrapper that can be run via npm/uvx or an installed binary. The install entries (node/uv packages named rollinggo) align with the described functionality.

Instruction Scope

SKILL.md confines runtime actions to invoking the rollinggo CLI and parsing its JSON output, and it documents flags and workflows. It does not instruct reading unrelated files or env vars. However, the default policy is to run the newest release on every run (npx --package rollinggo@latest or uvx --refresh), which means the agent will fetch and execute remote package code at runtime — this increases supply‑chain risk and runtime variability.

Install Mechanism

Install uses public package managers (npm/uv) and references package name 'rollinggo' — these are traceable registry installs rather than arbitrary URL downloads, which is reasonable for a CLI. The use of npx/uvx to run latest-by-default is convenient but results in transient execution of remote code each run; consider pinning versions for stability and security.

Credentials

Only one environment variable/credential is required: RollingGo_API_KEY (declared as primaryEnv). That is proportionate for a third‑party API CLI that needs an API key. No unrelated secrets or config paths are requested.

Persistence & Privilege

Skill does not request 'always' presence, does not declare system config paths, and does not modify other skills. Default autonomous invocation is allowed (platform default) but not combined with any additional privileged settings.

Assessment

This skill appears to do what it says: run the RollingGo CLI to search and inspect hotels and it only needs your RollingGo_API_KEY. Before installing, consider: (1) the SKILL defaults to executing the latest package via npx/uvx on every run — that means code from the npm/uv registry will be fetched and run at runtime; if you need stability or want to reduce supply‑chain risk, prefer installing a pinned global/local version instead of using --package@latest or --refresh; (2) verify you trust the RollingGo provider and the npm/uv package named 'rollinggo' (check the package homepage/repo and npm/uv package pages); (3) confirm what the RollingGo_API_KEY grants (scope, rate limits, billing) and avoid reusing high‑privilege keys; (4) this skill does not request other system files or unrelated credentials. If you want higher assurance, inspect the rollinggo package source on its registry/repository before use.

RollingGo Hotel CLI

When to Use

✅ Use this skill when:

• Searching Candidates: User wants to find hotels near a specific city, landmark, or address (e.g., "Find hotels near Tokyo Disneyland").
• Complex Filtering: User needs to narrow down options using natural language queries combined with exact dates, guest count, star ratings, budget limits, or distance radius.
• Tag & Brand Matching: User wants to find hotels with specific attributes (e.g., "family friendly", "breakfast included", "Marriott") by first checking the tag dictionary to build exact filters.
• Deep Dive & Pricing: User wants to inspect detailed room plans, real-time pricing, cancellation policies, or availability for a specific hotel ID.
• Comparison & Evaluation: User wants to compare multiple candidate hotels based on returning structured data and current rates.
• Hotel Booking: User is ready to select a room and book a hotel. The returned booking URLs and detail page links can be provided to guide the user to complete their reservation.

❌ Don't use this skill when:

• User asks about non-hotel travel booking (flights, trains, transfers, car rentals).

API Key

Resolution order: --api-key flag → RollingGo_API_KEY env var.

No key yet? Apply at: https://mcp.agentichotel.cn/apply

Runtime

Choose based on user's environment. Load the matching reference file and keep it for the session.

• npm, npx, Node, or no preference: Load references/rollinggo-npx.md
• uv, uvx, PyPI, or Python: Load references/rollinggo-uv.md
• Parity check or both: Load both references

Default when unspecified → npm/npx (broader env compatibility).

Version Freshness (Always Latest)

Default policy for this skill: use the newest release on every run.

• npm/npx: npx --yes --package rollinggo@latest rollinggo ...
• uvx: uvx --refresh --from rollinggo rollinggo ...

If using an installed command instead of temporary execution, upgrade first:

• npm global: npm install -g rollinggo@latest
• uv tool: uv tool upgrade rollinggo

Primary Workflow

Run these steps in order unless the user is already at a later step.

1. Clarify: destination, dates, nights, occupancy, budget, stars, tags, distance
2. If tag filters needed → run hotel-tags first to get valid tag strings
3. Run search-hotels → parse JSON → extract hotelId
4. Run hotel-detail --hotel-id <id> for room plans and pricing
5. If results are weak → loosen filters and retry

Commands Quick Reference

# Discover tags
rollinggo hotel-tags

# Search hotels (minimum required flags)
rollinggo search-hotels \
  --origin-query "<user's natural language request>" \
  --place "<destination>" \
  --place-type "<value from --help>"

# Hotel detail with pricing
rollinggo hotel-detail \
  --hotel-id <id> \
  --check-in-date YYYY-MM-DD \
  --check-out-date YYYY-MM-DD \
  --adult-count 2 --room-count 1

# Discover all flags
rollinggo search-hotels --help
rollinggo hotel-detail --help

Key Rules

• --place-type must use exact values from rollinggo search-hotels --help
• --star-ratings format: min,max e.g. 4.0,5.0
• --format table allowed only on search-hotels; rejected by hotel-detail and hotel-tags
• --child-count must match the count of --child-age flags
• --check-out-date must be later than --check-in-date
• Prefer --hotel-id over --name whenever available

Output

• stdout → result payload (JSON by default)
• stderr → errors only
• Exit 0 success · 1 HTTP/network failure · 2 CLI validation failure
• Results include booking URLs and hotel detail page links for downstream use

Filter Loosening (when no results)

Try in order: remove --star-ratings → increase --size → increase --distance-in-meter → remove tag filters → widen dates or budget