Agent skill · software engineering · jeremylongshore
alchemy-install-auth
Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. Use when creating or repairing Alchemy connectivity. Trigger with "set up Alchemy", "configure an Alchemy API key", or "choose viem or Wallet APIs".
Why this skill is useful
Adds specific commands and configurations for setting up the Alchemy SDK for blockchain development that the AI wouldn't reliably generate on its own.
What it needs
Requires node, npm 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 Installation and Authentication Intake Overview Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. 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 The legacy alchemy-sdk JavaScript repository is archived and deprecated. New EVM reads use viem or direct documented HTTP APIs; transacting applications and Portfolio support use @alchemy/wallet-apis; Solana work uses Solana Web3.js. An application API key, an Admin access key, a Notify auth token, and a webhook signing key are different credentials and are not interchangeable. Authentication Prefer server-side request-header authentication for confidential workloads. A browser key is acceptable only when the current Alchemy guidance, explicit domain allowlists, least privilege, and the product threat model allow it; short-lived JWTs are the stronger frontend option. Store Admin, Notify, webhook, and signing credentials only in approved secret storage. Instructions 1. Classify the requested capability as Node RPC, Data API, Portfolio, Wallet APIs, Notify management, webhook receipt, Admin usage, or Solana. 2. Confirm the required chain and feature in the live supported-chain and feature-support matrices; do not infer feature parity from RPC support. 3. Select viem, direct HTTP, @alchemy/wallet-apis, or Solana Web3.js from the capability—not from the archived SDK examples. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-install-auth