Pp Rakuten Travel

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/travel/rakuten-travel/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Rakuten Travel

Prerequisites: Install the CLI

This skill drives the rakuten-travel-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install rakuten-travel --cli-only

2. Verify: rakuten-travel-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/travel/rakuten-travel/cmd/rakuten-travel-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Search Rakuten Travel public pages, inspect property details and compare bounded date alternatives. Keep room and plan identities, source price labels and booking links intact.

Build from source

From this repository directory:

go build -o bin/rakuten-travel-pp-cli ./cmd/rakuten-travel-pp-cli
export PATH="$PWD/bin:$PATH"

The public website backend needs no API credentials or browser.

When to Use This CLI

Use for accommodation discovery in Japan, dated room-plan inspection, or bounded hotel/date comparisons on Rakuten Travel. The user completes booking on Rakuten.

Anti-triggers

Use another workflow for cross-provider comparisons, reservation/payment/cancellation execution, account management, automatic destination translation, radius search, or unequal party allocations across rooms.

Workflow

1. Establish destination or hotel, check-in/out dates, room count, adults per room and the six child categories. Resolve missing details before inventory search. Counts are per room; rooms must share the same party. Confirm category choices rather than infer ages.
2. Resolve source IDs with areas list or hotels search. Keep ambiguous area choices visible. Japanese labels and English literal keywords may return different coverage. Continue when candidates have hotel IDs and source URLs.
3. Inspect shortlisted properties with hotels show, including amenities, access and fee/policy notes. Continue when material requirements are verified or explicitly unknown.
4. Run offers search with explicit dates and party. Preserve hotel/plan/room IDs and source quote units. Follow returned within-page offset before the next source page when more results are needed; keep the request budget bounded.
5. Inspect a chosen tuple with offers show. Use compare only for an explicit matrix of hotel IDs and check-in dates with equal stay length and party, at most nine cells. Keep failed and empty cells distinct.
6. Present source-labelled prices, dates, per-room party, meals, material unknown fees/policies, freshness and the returned Rakuten link. Complete when each recommended option has enough evidence for the traveler to confirm and book on Rakuten.

For price units, cache states, policy scope or ambiguous empty results, read the data contract before interpreting output.