Agent skill · software engineering · jeremylongshore
alchemy-sdk-patterns
Route Alchemy work to viem, direct Data APIs, Wallet APIs v5, or Solana Web3.js without reviving the archived SDK. Use when designing shared clients and adapters. Trigger with "Alchemy SDK pattern", "replace alchemy-sdk", or "choose an Alchemy client".
Why this skill is useful
Adds production-ready scripts for multi-chain client factories, response caching, and typed NFT queries that significantly enhance blockchain application development.
What it needs
Requires alchemy-sdk installed locally. Requires alchemy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Alchemy Client and API Routing Patterns Overview Route Alchemy work to viem, direct Data APIs, Wallet APIs v5, or Solana Web3.js without reviving the archived SDK. 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 There is no single current JavaScript Alchemy SDK for every product. EVM Node reads belong behind a viem transport adapter, Data APIs behind response-contract adapters, transacting applications behind Wallet APIs v5, and Solana behind Solana Web3.js. The archived alchemy-sdk is migration input, not a new architecture choice. Authentication Each adapter declares the credential it accepts and rejects other credential classes. Keep application keys, Admin access keys, Notify tokens, webhook signing keys, and wallet signing authority in separate types and secret paths. Instructions 1. Inventory each existing call by capability, chain, runtime, side effect, data owner, and credential class. 2. Assign Node RPC calls to a typed viem public client and keep the configured chain adjacent to the transport. 3. Assign NFT, Transfers, Prices, Simulation, or Portfolio calls to a narrow HTTP adapter that validates the documented response and pagination contract. 4. Assign smart-wallet creation and transaction flows to the current Wallet APIs v5 surface; isolate signing policy from data reads. 5. Represent partial success, pagination, retryability, and unsupported-chain outcomes explicitly instead of returning null or an untyped provider exception. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-sdk-patterns