alchemy-upgrade-migration
Migrate from alchemy-sdk v2 to v3 and handle breaking changes. Use when upgrading Alchemy SDK versions, migrating from deprecated alchemy-web3, or adapting to new API patterns. "migrate alchemy-web3", "alchemy breaking changes". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill alchemy-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Alchemy Upgrade & Migration ## Overview Migration guide for Alchemy SDK upgrades and deprecated package transitions. The `alchemy-web3` package is deprecated — migrate to `alchemy-sdk`. ## Migration Paths | From | To | Complexity | |------|----|-----------| | `alchemy-web3` | `alchemy-sdk` | High (different API surface) | | `alchemy-sdk` v2 → v3 | `alchemy-sdk` v3 | Medium (some breaking changes
What does the alchemy-upgrade-migration skill do?
Migrate from alchemy-sdk v2 to v3 and handle breaking changes. Use when upgrading Alchemy SDK versions, migrating from deprecated alchemy-web3, or adapting to new API patterns. "migrate alchemy-web3", "alchemy breaking changes". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill alchemy-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
