Agent skill · mvanhorn
pp-activity-japan
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages. Use for an Activity Japan itinerary shortlist; destination search is access gated.
What it needs
About 4k tokens when loaded.
What this skill does
<!-- 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: 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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/pp-activity-japan