Agent skill · software engineering · jeremylongshore
podium-multi-location-router
Route Podium API calls across multiple physical locations with strict
Why this skill is useful
Adds a comprehensive routing layer with executable scripts for managing Podium API calls across multiple locations, ensuring credential isolation and audit trails that are not covered in public documentation.
What it needs
Requires bash, curl, grep, jq, python3, sqlite3 installed locally. Requires podium account access. About 9k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Podium Multi-Location Router Overview Route Podium API calls across multiple physical locations and operate the routing layer in production. This is not a tutorial on Podium's location model — it is the per-location dispatch code your integration runs when Sydney and Burleigh Heads share a single OAuth app, when an agency onboards five new stores in one afternoon, and when a compliance auditor walks in and asks "which location's webchat received that contact write at 14:07 UTC last Tuesday." The six production failures this skill prevents: 1. Writes to wrong location silently — Sydney's contact write lands on Burleigh Heads' contact list because the calling code resolved locationuid from a stale lookup or hard-coded the wrong UID. The Podium API accepts it, returns 200, and the data sits in the wrong location with no error surface. Naive integrations discover this when a customer reports "I'm getting review requests for a store I've never been to." 2. Credential cross-contamination — Sydney's OAuth token gets reused for a write to Burleigh Heads. The Podium API does not reject this because the OAuth app is org-scoped and both locations live under the same org. The write succeeds; the audit trail attributes it to Sydney's credential; post-incident forensics cannot tell whether the write was authorized by Sydney's operator or by a bug. 3. Audit trail missing location-ID — log lines say wrote contact name=Jane Doe without saying which locationuid received the write. When a compliance question lands months later, the integration cannot answer "which location received this customer's data?" The answer determines GDPR data-subject scope and PCI cardholder-data exposure. 4. Bulk onboarding race condition — onboarding 5 new locations in one operation spawns 5 OAuth authorization flows. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/podium-multi-location-router--866c05