Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/alchemy-upgrade-migration

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/alchemy-upgrade-migration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈78 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈802 more on demand in 1 file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈311 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Canary one capability at a time with stop thresholds and the old artifact still deployable; remove deprecated imports only after parity and negative paths pass.
  6. Update runbooks, CI bans, lockfiles, observability, owners, and rollback; separately follow the current Wallet APIs v5 guide for v4 consumers.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, wallet addresses, customer data, plan changes, spend, key creation or rotation, webhook changes, deployment, replay, transaction construction, signing, broadcast, or deletion.

Approval Boundaries

Architecture approves target routing; security approves changed credential and signing boundaries; release/product approve canary and normalized differences. Production transaction migration requires explicit wallet-policy approval.

Error Handling

  • Do not replace the archived SDK with one universal wrapper that hides product-specific contracts.
  • Do not treat different pagination, partial-error, finality, or numeric semantics as cosmetic parity.
  • If a canary breaches correctness, completeness, latency, error, or spend thresholds, route back to the prior artifact.

Output

Return the legacy call inventory, target routing, credential delta, parity schema, fixture/dual-read evidence, canary thresholds, deprecated-import gate, rollout sequence, unresolved differences, and rollback receipt. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Migrate an alchemy.core.getBalance call to a viem public client and compare normalized values and chain IDs before switching traffic.
  • Migrate Portfolio behavior only after proving the replacement preserves top-level partialErrors and fresh retry of failed networks.

Validation

Exercise and record expected and observed results for:

  • archived import scan
  • numeric parity
  • pagination parity
  • partial-error parity
  • wrong credential boundary
  • canary rollback

Resources

  • Current first-party evidence map — recheck dated Alchemy sources before execution.
  • Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides safe and standard instructions for migrating between versions of the Alchemy SDK. It follows best practices by using environment variables for API keys and referencing official, well-known packages.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<source-client> <capability-set> <release-scope>
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "alchemy",
  "migration",
  "viem"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/alchemy-upgrade-migration