Agent skill · software engineering · jeremylongshore
instantly-upgrade-migration
Upgrade Instantly SDK, CLI, OpenAPI-derived types, or API v2 contracts with controlled compatibility testing. Use when dependencies or current API v2 schemas change after the initial v1 migration. Trigger with "upgrade the Instantly SDK", "refresh Instantly OpenAPI types", or "test an Instantly API change".
Why this skill is useful
Adds migration scripts and detailed endpoint mappings for transitioning from Instantly API v1 to v2, which are not publicly documented.
What it needs
Requires npm installed locally. Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Upgrade Instantly SDK and API Contracts Overview Handle ongoing tooling and schema evolution separately from the one-time API v1 cutover. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract The TypeScript SDK is beta and may receive refinements before stable 1.0.0. The CLI and SDK have different Node.js minimums and release cadences. Generated resources follow the live OpenAPI schema; method availability must be checked in the installed version. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Inventory current runtime, package pins, generated types, routes, fixtures, and consumers. 2. Read first-party release/package metadata and classify breaking, additive, and behavioral changes. 3. Update one component in an isolated branch and retain the previous lockfile for rollback. 4. Run offline type, contract, error, pagination, and redaction tests. 5. Canary a bounded read-only staging operation. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-upgrade-migration