How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

japan-timed-tickets - Skill

Name: japan-timed-tickets
Author: mvanhorn

Imported from mvanhorn/printing-press-library (library/travel/japan-timed-tickets/AGENTS.md). Install upstream with npx skills add mvanhorn/printing-press-library --skill japan-timed-tickets. Copyright stays with the author.

Japan Timed Tickets Printed CLI Agent Guide

This directory is a generated japan-timed-tickets-pp-cli printed CLI. It was produced by CLI Printing Press, so treat systemic fixes as upstream Printing Press fixes first. Keep local edits narrow and document why a generated-tree patch belongs here.

Local Operating Contract

Start by asking the generated CLI for current runtime truth:

japan-timed-tickets-pp-cli doctor --json
japan-timed-tickets-pp-cli agent-context --pretty

Use runtime discovery instead of relying on a copied command list:

japan-timed-tickets-pp-cli which "sunset slots" --json
japan-timed-tickets-pp-cli onsale --help

Add --agent to command invocations for JSON, compact output, non-interactive defaults, and no color:

japan-timed-tickets-pp-cli onsale --date 2026-11-24 --agent

This CLI is read-only: it never buys, adds to cart, logs in or joins a waiting room. --dry-run previews a command without network calls:

japan-timed-tickets-pp-cli availability teamlab-kyoto --date 2026-11-24 --dry-run --agent

--yes applies only to the local profile delete. --agent does not imply --yes.

Novel Command Data Sources

Every hand-written novel command must declare its strategy in a Go line comment:

// pp:data-source auto

Use exactly one of auto, local, live, or computed. Keep auto when the command honors --data-source auto|local|live by preferring live data with a local fallback; use local for local-only reads, live for remote-only reads, and computed for pure computation from embedded rules. Change a generated scaffold's auto default deliberately when its implementation has a narrower source, and keep cmd.Annotations["pp:data-source"] on the same command in sync; --agent envelopes read that annotation for meta.source. Reject incompatible --data-source requests with a clear error. TODO stubs still fail dogfood even when annotated.

Platform Credential References

Normal API authentication is separate from optional platform-source credential resolution. If this CLI uses indirect references for a tenant-gated platform source, add the downstream registration in a preserved hand-authored file under internal/cli/ and provide both CredentialResolverFactory and ValidateSourceProfile on platformSourceRegistration for any selected source that has references. A source with no references may omit both hooks and receives an empty credential map. Keep reference values opaque to shared profile code, validate only the selected source in the downstream hook, and never persist resolved credential bytes. Do not edit generator-owned internal/platform packages; a reprint refreshes those files while retaining the downstream registration file.

For install, auth, examples, and longer product guidance, read README.md and SKILL.md. This file intentionally stays small so repo-local agents get invariant local guidance without duplicating the generated docs.

Release Ledger

CHANGELOG.md and .printing-press-release.json are the public library's per-CLI release ledger. Fresh prints carry an unstamped runtime version such as 0.0.0-dev; the final YYYY.M.N CLI release version is assigned only after a publish PR merges in mvanhorn/printing-press-library. Do not hand-bump those files or edit var version = ... for release bookkeeping; preserve existing ledger files on reprint and let the library workflow stamp the next release.

Local Customizations

This directory is generated output -- a fresh print can overwrite the whole tree, so ad-hoc hand-edits don't survive on their own. If you modify the generated code, record each change under .printing-press-patches/ (parallel to .printing-press.json). Regen and publish-validate read those records and fail closed when a recorded file or call site is gone, so a dropped customization cannot ship as if it were still applied.

The entry shape, and the altitude to write it at -- a durable reprint-guard, not a changelog -- live in the public library's AGENTS.md, which is the single source of truth; this guide intentionally doesn't duplicate them.

Install japan-timed-tickets and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "mvanhorn-printing-press-library-japan-timed-tickets", "kind": "skill", "name": "japan-timed-tickets", "description": "This directory is a generated `japan-timed-tickets-pp-cli` printed CLI. It was produced by [CLI Printing Press](https://github.com/mvanhorn/cli-printing-press), so treat systemic fixes as upstream Printing Press fixes first. Keep local edits narrow and document why a generated-tree patch belongs here.", "publisher": "mvanhorn", "version": "1.0.0", "capabilities": { "domains": [ "creative", "legal" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This directory is a generated `japan-timed-tickets-pp-cli` printed CLI. It was produced by [CLI Printing Press](https://github.com/mvanhorn/cli-printing-press), so treat systemic fixes as upstream Printing Press fixes first. Keep local edits narrow and document why a generated-tree patch belongs here." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/mvanhorn/printing-press-library", "path": "library/travel/japan-timed-tickets/AGENTS.md", "ref": "a09fb04aee97081e58c9550b672989c2e7ab8e79", "url": "https://github.com/mvanhorn/printing-press-library/blob/a09fb04aee97081e58c9550b672989c2e7ab8e79/library/travel/japan-timed-tickets/AGENTS.md", "key": "mvanhorn/printing-press-library/library/travel/japan-timed-tickets/AGENTS.md" } }, "instructions": "# Japan Timed Tickets Printed CLI Agent Guide\n\nThis directory is a generated `japan-timed-tickets-pp-cli` printed CLI. It was produced by [CLI Printing Press](https://github.com/mvanhorn/cli-printing-press), so treat systemic fixes as upstream Printing Press fixes first. Keep local edits narrow and document why a generated-tree patch belongs here.\n\n## Local Operating Contract\n\nStart by asking the generated CLI for current runtime truth:\n\n```bash\njapan-timed-tickets-pp-cli doctor --json\njapan-timed-tickets-pp-cli agent-context --pretty\n```\n\nUse runtime discovery instead of relying on a copied c", "cost": { "context_tokens": 1058 } }

japan-timed-tickets

About

Japan Timed Tickets Printed CLI Agent Guide

Local Operating Contract

Novel Command Data Sources

Platform Credential References

Release Ledger

Local Customizations

Install japan-timed-tickets and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews