pp-ticketmaster

<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/media-and-entertainment/ticketmaster/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/". --> # Ticketmaster — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `ticketmaster-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: ```bash npx -y @mvanhorn/printing-press-library install ticketmaster --cli-only ``` 2. Verify: `ticketmaster-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.5 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/media-and-entertainment/ticketmaster/cmd/ticketmaster-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. ticketmaster-pp-cli is the first single-binary CLI for the Ticketmaster Discovery API. It absorbs the full read-only surface (events, venues, attractions, classifications, suggest) and adds a local SQLite store with FTS search, named watchlists, residency collapse, tour-view with on-sale flags, and markdown briefs — the workflows real users built scripts to handle. ## When to Use This CLI Reach for this CLI when a user asks 'what's on at <venue/metro>', 'where is <artist> playing', or 'what concerts this weekend'. Best for repeat queries against curated venue/artist watchlists (offline FTS shines here), residency-heavy venues (opera, Broadway, comedy), and agent contexts where compact JSON output keeps token usage low. Skip when checkout/purchase is needed — that requires the Commerce API, which this CLI does not cover. ## When Not to Use This CLI Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Local-store aggregations - **`events upcoming`** — Fan out across a venue ID file or list and return one merged, deduplicated, date-sorted event list — the watchlist primitive behind any curated 'what's on at my venues' workflow. _When the user has a curated list of venues they care about and wants one merged feed; replaces hand-rolled per-venue fan-out scripts._ ```bash ticketmaster-pp-cli events upcoming --venue-ids KovZ917Ahkk,KovZpZAFkvEA --days 60 --json ``` - **`events residency`** — Collapse runs of same-name + same-venue events into one row per residency with first_date, last_date, night_count, and id_list — so a 16-night opera season shows as one entry, not 16. _When listing upcoming events would otherwise show many near-duplicate rows for Broadway tours, opera seasons, or comedy residencies._ ```bash ticketmaster-pp-cli events residency --window 28 --json ``` - **`events by-classification`** — Local join of events × classifications, grouped by segment and genre, with event count and three example events per leaf — the bucketed view newsletter authors and local-scene trackers reach for. _When summarizing 'what's on this month' broken down by music vs theatre vs comedy vs sports._ ```bash ticketmaster-pp-cli events by-classification --dma 383 --window 60 --json ``` - **`events watchlist`** — Save, list, run, and remove named filter sets (venue IDs, attraction IDs, segments, DMA IDs) that persist across runs in the local SQLite store — the generic primitive any curated 'my venues' workflow composes from. _When the same curated venue/artist/genre filter recurs across many queries._ ```bash ticketmaster-pp-cli events watchlist save seattle --venue-ids KovZ917Ahkk,KovZpZAFkvEA,KovZpZA1klkA ``` - **`events price-bands`** — Bucket events by priceRanges.min into <$50 / $50-100 / $100-200 / $200+ bands and report count + sample events per band, grouped by classification. _When the user wants to know where the affordable shows are this month, or how a venue's pricing skews._ ```bash ticketmaster-pp-cli events price-bands --dma 383 --window 30 --json ``` ### Tour & on-sale tracking - **`events tour`** — For a given attraction (artist/team/touring show), return every upcoming event sorted by date, with city, venue, on-sale status, and a flag for events going on-sale within 7 days. _When tracking an artist across cities or watching for presale windows._ ```bash ticketmaster-pp-cli events tour KovZ917Ahkk --on-sale-window 7 --json ``` - **`events on-sale-soon`** — Local query for events whose public on-sale falls in the next N days, sorted ascending — the canonical 'presale watch' view that no API endpoint provides. _When the user wants to be alerted to upcoming on-sale dates without polling each artist manually._ ```bash ticketmaster-pp-cli events on-sale-soon --window 7 --classification rock --json ``` - **`events presales`** — Query Ticketmaster's real `sales.presales[]` windows and classify each as upcoming, open, or ended. Filter by artist, city, venue, classification, and hours until opening. ```bash ticketmaster-pp-cli events presales --keyword "The National" --status upcoming --opens-within 48 --json ``` - **`events checkout`** — Print the best official checkout URL for an event, preferring an open or named presale. Add `--launch` to open it; the command never reserves inventory or buys unattended. ```bash ticketmaster-pp-cli events checkout G5diZ9YpV7fJb --presale "Artist Presale" ``` ### Agent-native plumbing - **`events dedup`** — Read an event JSON array from stdin or the local store, apply a deduplication strategy (name+venue+date, or tour-leg), and write the deduped stream to stdout — composes with any upstream command. _When merging results from multiple queries or sources and the duplicates need to be removed before agent processing._ ```bash ticketmaster-pp-cli events list --keyword phish --json | ticketmaster-pp-cli events dedup --strategy tour-leg ``` - **`events brief`** — Render a markdown 'what's on' report grouped by night → venue → events with classification labels and price bands, suitable for newsletter, Obsidian, iMessage, or agent context. _When the user needs a paste-ready event summary for a chat thread, newsletter, or LLM context._ ```bash ticketmaster-pp-cli events brief --dma 383 --window 7 ``` ## Command Reference **attractions** — Manage attractions - `ticketmaster-pp-cli attractions find` — Find attractions (artists, sports, packages, plays and so on) and filter your search by name, and much more. - `ticketmaster-pp-cli attractions get` — Get details for a specific attraction using the unique identifier for the attraction. **classifications** — Manage classifications - `ticketmaster-pp-cli classifications get` — Get details for a specific segment, genre, or sub-genre using its unique identifier. - `ticketmaster-pp-cli classifications get-genre` — Get details for a specific genre using its unique identifier. - `ticketmaster-pp-cli classifications get-segment` — Get details for a specific segment using its unique identifier. - `ticketmaster-pp-cli classifications get-subgenre` — Get details for a specific sub-genre using its unique identifier. - `ticketmaster-pp-cli classifications list` — Find classifications and filter your search by name, and much more. **events** — Manage events - `ticketmaster-pp-cli events get` — Get details for a specific event using the unique identifier for the event. - `ticketmaster-pp-cli events list` — Find events and filter your search by location, date, availability, and much more. **suggest** — Manage suggest - `ticketmaster-pp-cli suggest` — Find search suggestions and filter your suggestions by location, source, etc. **venues** — Manage venues - `ticketmaster-pp-cli venues get` — Get details for a specific venue using the unique identifier for the venue. - `ticketmaster-pp-cli venues list` — Find venues and filter your search by name, and much more. ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash ticketmaster-pp-cli which "<capability in your own words>" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. ## Recipes ### Seattle watchlist composition (no Seattle-specific code in the CLI) ```bash ticketmaster-pp-cli events watchlist save seattle --venue-ids KovZ917Ahkk,KovZpZAFkvEA,KovZpZA1klkA,KovZpZAFEdeA,KovZpZAFkv1A ``` Save a named watchlist of Seattle venue IDs. Then run "events watchlist run seattle --days 60 --json" to apply the filter across upcoming events; pipe through "events dedup --strategy name-venue-date" for the final cleaned feed. Replaces a 595-line bash script. ### Track an artist across all upcoming dates with on-sale flags ```bash ticketmaster-pp-cli events tour KovZ917Ahkk --on-sale-window 7 --json --select 'name,dates.start.localDate,_embedded.venues[0].name,_embedded.venues[0].city.name,sales.public.startDateTime' ``` Returns every upcoming tour stop with city, venue, and a flag for stops going on-sale within a week. The --select narrows the deeply-nested Discovery payload to just what an agent needs. ### Weekend brief for a metro ```bash ticketmaster-pp-cli events brief --dma 383 --window 3 --classification music ``` Render a markdown brief of the next 3 days of music events in Seattle-Tacoma (DMA 383) - paste-ready for Obsidian or an iMessage thread. ### On-sale watch for rock shows ```bash ticketmaster-pp-cli events on-sale-soon --window 14 --classification rock --json ``` Two-week-out scan for rock events going on public sale; pipe to an alerting script. ## Auth Setup Authentication is a single Ticketmaster Discovery API consumer key, passed as the `apikey` query parameter on every request. Register at https://developer-acct.ticketmaster.com and copy the Consumer Key from your My Apps dashboard. Set TICKETMASTER_API_KEY in your shell environment. The free tier allows 5000 requests/day at 5/second. Run `ticketmaster-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`. - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash ticketmaster-pp-cli attractions get mock-value --agent --select id,name,status ``` - **Previewable** — `--dry-run` shows the request without sending - **Offline-friendly** — sync/search commands can use the local SQLite store when available - **Non-interactive** — never prompts, every input is a flag - **Read-only** — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": <data> } ``` Parse `.results` for data and `.meta.source` to know whether it's live or local. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home <dir>` for one invocation, or set `TICKETMASTER_HOME=<dir>` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `TICKETMASTER_CONFIG_DIR`, `TICKETMASTER_DATA_DIR`, `TICKETMASTER_STATE_DIR`, `TICKETMASTER_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `TICKETMASTER_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `credentials.toml`, `data.db`, cookies, and auth sidecars. `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. - Stored secrets live in `credentials.toml` under the data dir. Existing legacy `config.toml` secrets are read for compatibility and leave `config.toml` on the first auth write. - Run `ticketmaster-pp-cli doctor --fail-on warn` to surface path and credential-location warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "ticketmaster": { "command": "ticketmaster-pp-mcp", "env": { "TICKETMASTER_HOME": "/srv/ticketmaster" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `TICKETMASTER_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `TICKETMASTER_HOME`, or `doctor` will not find credentials left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, run: ```bash ticketmaster-pp-cli recall "<user's question>" --agent ``` The response envelope: ```json { "query": "...", "normalized": "<normalized form>", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "resource_id": "...", "resource_type": "...", "venue": "...", "confidence": 2, "entity_match": "exact|partial|unknown", "source": "taught|preseed|pattern", "warnings": ["..."] } ], "mismatches": [ /* only when --debug-mismatches */ ], "warnings": [ /* top-level */ ], "candidates": [ { "id": 12, "class": "flag_alias | playbook_candidate", "summary": "...", "sightings": 3, "last_seen": "...", "rationale": "...", "next_action": ["<trial command>", "ticketmaster-pp-cli learnings confirm 12"] } ], "playbook": { "query_family": "...", "playbook": { "steps": [ { "cmd": "<command with {slot} substitution>", "purpose": "..." } ], "entity_slots": ["$ENTITY"], "expected_tool_calls": 3 }, "slots_resolved": { "$ENTITY": { "token": "<live token>", "canonical": "<canonical>" } }, "notes": "<workarounds + gotchas for this query family>" },