Pp Activity Japan

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/travel/activity-japan/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/". -->

Activity Japan plan inspection

Use the installed activity-japan-pp-cli binary. In a source checkout, build with go build -o ./bin/activity-japan-pp-cli ./cmd/activity-japan-pp-cli, add ./bin to PATH, and verify activity-japan-pp-cli --version. The installer below applies to released library packages. Run leaf --help when a flag is unclear.

Prerequisites: Install the CLI

This skill drives the activity-japan-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 activity-japan --cli-only

2. Verify: activity-japan-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/activity-japan/cmd/activity-japan-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.

Inspect Activity Japan plans and future dates in compact JSON. Compare a bounded shortlist against traveler constraints and carry source uncertainty through booking handoff.

Workflow

1. Get a plan ID from the traveler or an Activity Japan /publish/plan/<id> URL. If they only give a destination or activity type, use the Activity Japan website to identify IDs; CLI search pages are currently WAF challenged.
2. Run experience detail ID --lang en --agent. Keep name_original_ja, operator_id, option IDs, meeting point, venue, restrictions, cancellation text, and missing separate. The website locale and locale_support_flag do not establish spoken guide languages.
3. For an itinerary date, run experience sessions ID --date YYYY-MM-DD --agent, then experience price ID --date YYYY-MM-DD --adults N --agent. Use --option ID to inspect one selected price option. A zero yen child or infant option is not an adult price.
4. If an exact per-person session needs a stock recheck, pass its current session_id to experience check ID --date YYYY-MM-DD --session ID --adults N --agent. Treat the result as an observation. Group-priced quantity checks are refused because the source count basis is unverified.
5. For 2–5 known IDs, run experience compare ID ID --date YYYY-MM-DD --adults N --age A --max-jpy B --agent. Use --max-minutes N only for total experience duration; mixed source prose remains unknown. unknown is not a match. A subtotal below a budget remains unknown when mandatory fees are unpriced.
6. Before handoff, run inventory languages ID --agent and experience handoff ID --lang en --agent. experience brief includes a verified canonical URL when the selected language is indexed; otherwise it marks the URL unresolved.

Done when the answer names the exact plan and option where relevant, source URL, Asia/Tokyo observation time, price unit and age band, dated availability state, and unresolved conditions. Never call an observation a reservation.