Agent skill · software engineering · jeremylongshore
persona-upgrade-migration
Migrate between dated Persona API versions using inventory, contract fixtures, dual-read evidence, and rollback. Use when changing Persona-Version. Trigger with: "upgrade Persona API", "migrate Persona version", "update Persona-Version".
Why this skill is useful
Provides specific commands and patterns for upgrading Persona API versions that the AI wouldn't reliably generate on its own.
What it needs
Requires persona account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Dated Persona API Version Migration Overview Treat Persona-Version as a contract migration. Because the request header overrides the key’s configured version and compatible releases can add or reorder data, migrate parsers, webhook handling, and operational evidence together. Prerequisites Source and target dated API versions Endpoint, resource, event, and consumer inventory Representative redacted fixtures plus a reversible rollout mechanism Instructions Step 1: Freeze the baseline Record API-key configured versions, explicit headers, endpoints, templates, response hashes, events, dashboards, and consumer assumptions. Step 2: Read the provider delta Map documented breaking and compatible changes to each request, JSON:API mapper, event handler, policy rule, test, and data export. Step 3: Harden for additions Make parsers tolerate new resources, fields, types, event types, and array ordering before switching the header. Step 4: Build dual-version fixtures Capture or synthesize equivalent source and target responses for success, error, pagination, inquiry sessions, verifications, and webhooks. Step 5: Canary the explicit header Send the target Persona-Version for a bounded cohort and compare transport, resource, event, decision, latency, and quota metrics. Step 6: Promote with rollback Change the explicit header and key configuration deliberately, retain source-version compatibility during the observation window, and document the rollback trigger. Authentication Test source and target versions with appropriately scoped keys. The explicit request header is authoritative for that request, so accidental fallback to a key default is a gate failure. Tool Discipline Use Read and Grep to inspect application configuration, provider documentation, fixtures, schemas, tests, and redacted operational evidence before proposing a change. Use Write or Edit only for an approved implementation, configuration, test, runbook, or redacted receipt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/persona-upgrade-migration