Agent skill · software engineering · jeremylongshore
clari-upgrade-migration
Migrate a Clari integration across hosts, versions, endpoint contracts, or export schemas with dual-read comparison and rollback. Use when retiring legacy clients or mappings. Trigger with: "upgrade Clari API", "migrate a Clari client", "handle Clari schema drift".
Why this skill is useful
Adds specific commands and scripts for handling Clari API version migrations and schema changes that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires clari account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari API and Schema Migration Overview Treat provider URL, authentication, request schema, job behavior, response schema, and destination mapping as one versioned contract. Prove the target alongside the current path before moving production traffic or published data. Prerequisites Current and target hosts, versions, operations, schemas, and credential types Representative requests and expected reconciliations Dual-run environment, migration owner, and rollback deadline Instructions Step 1: Inventory the delta Diff hosts, base paths, auth headers, methods, fields, enum values, errors, limits, pagination, and mutation semantics. Step 2: Build an explicit mapping Classify every used field and behavior as unchanged, renamed, transformed, added, removed, or unsupported. Step 3: Update clients and fixtures Pin the target contract, add target adapters and schemas, and retain current fixtures for regression and rollback testing. Step 4: Dual-read safely Run bounded non-production or approved parallel reads for identical windows and compare identifiers, counts, values, states, and latency. Step 5: Cut over atomically Move one workload or consumer at a time, retain the prior client and published snapshot, and stop on unexplained divergence. Step 6: Retire with evidence After the rollback window, remove legacy credentials and routes, update runbooks, and retain the comparison and revocation receipts. Authentication Do not reuse headers merely because two surfaces belong to Clari. Revenue, v2 ingestion, and Copilot each require their documented host and credentials; rotate or revoke legacy credentials only after rollback is no longer needed. Tool Discipline Use Read and Grep to inspect configuration, provider contracts, fixtures, logs, schemas, and existing tests before proposing a change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-upgrade-migration