Agent skill · software engineering · jeremylongshore
alchemy-upgrade-migration
Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence. Use when removing alchemy-sdk or upgrading Wallet APIs. Trigger with "migrate alchemy-sdk", "replace alchemy-web3", or "upgrade Wallet APIs to v5".
Why this skill is useful
Provides specific migration commands and patterns for transitioning between Alchemy SDK versions that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Alchemy Archived SDK Migration Overview Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence. This workflow produces a reviewable artifact and negative-path evidence before any live side effect. Prerequisites Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle. Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope. Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary. Current Contract alchemy-sdk is deprecated and its repository is archived. Current migration targets are capability-specific: viem for JavaScript EVM RPC, direct documented Data API adapters, @alchemy/wallet-apis for transacting apps and Portfolio support, and Solana Web3.js for Solana. Wallet APIs v5 has a separate first-party migration guide. Authentication Inventory every credential the old client could access and grant each replacement adapter only its needed class. Do not let migration move secrets from a server boundary to browser code or merge read and signing authority. Instructions 1. Freeze dependency locks and inventory every alchemy-sdk, alchemy-web3, endpoint, namespace, WebSocket, Notify, Data API, Wallet, and signer use by capability and side effect. 2. Route EVM RPC to viem, product HTTP calls to typed adapters, transacting/Portfolio use to Wallet APIs v5 where applicable, and Solana use to Solana Web3.js. 3. Define normalized parity contracts for values, pagination, partial errors, retryability, chain identity, subscriptions, and transaction intent; preserve raw evidence for differences. 4. Build fixtures and dual-read comparison for read-only paths; use simulation/testnet and explicit authorization for transaction paths. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-upgrade-migration