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

/alchemy-sdk-patterns

@820dfc8
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.4% 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 ≈275 characters, or 3.4%.

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 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. Add contract fixtures for success and every documented failure class, then ban new alchemy-sdk imports with a focused repository test.

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 owns capability routing and adapter boundaries. Security owns credential types and signing policy. Replacing a production provider or transaction path requires a canary and rollback approval.

Error Handling

  • Do not wrap every Alchemy product in a generic client that erases pagination, partial errors, or credential distinctions.
  • Do not convert a partial Portfolio response into complete success.
  • Do not let a read adapter gain wallet signing authority for convenience.

Output

Return the call inventory, capability routing table, typed adapter contracts, credential separation, error algebra, fixture matrix, deprecated-import gate, migration order, and rollback boundaries. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Route eth_getBalance through a viem public client while routing multi-chain holdings through a Portfolio adapter that surfaces partialErrors.
  • Keep Wallet APIs transaction construction behind a separately approved signer boundary rather than extending a generic read client.

Validation

Exercise and record expected and observed results for:

  • unsupported chain
  • partial Portfolio success
  • pagination continuation
  • rate limit
  • wrong credential class
  • archived import reintroduced

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 standard production-ready patterns for using the Alchemy SDK in Web3 applications, including client factories, caching layers, and error handling. No security issues were detected.

  • 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
<capability> <runtime> <chain-set>
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "alchemy",
  "architecture",
  "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-sdk-patterns