Agent skill · marketing growth · jeremylongshore
instantly-migration-deep-dive
Plan and execute a governed Instantly API v1-to-v2 migration with endpoint and key inventory. Use when replacing deprecated v1 calls and incompatible keys before cutover. Trigger with "migrate Instantly v1 to v2", "inventory deprecated Instantly endpoints", or "plan an Instantly API cutover".
Why this skill is useful
Provides detailed migration strategies and specific code snippets for integrating with Instantly.ai that the AI wouldn't generate on its own.
What it needs
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
Instantly API v1-to-v2 Cutover Overview Move a production integration from deprecated API v1 to incompatible API v2 without silent behavior drift. 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 API v1 was deprecated on January 19, 2026; new integrations use API v2. API v2 needs a new scoped bearer key and is not compatible with v1 keys. Methods, paths, field naming, pagination, and several asynchronous operations changed. 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 every v1 endpoint, key, consumer, schedule, owner, and failure policy. 2. Map each call to the official migration table and required v2 scope. 3. Build v2 request/response contract tests for methods, snakecase fields, cursors, and background jobs. 4. Issue separate v2 keys and dual-read only where privacy and consistency controls allow it. 5. Canary one workflow, compare outcomes, then cut over consumers in bounded phases. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-migration-deep-dive