Agent skill · software engineering · jeremylongshore
alchemy-core-workflow-a
Design a multi-chain holdings workflow on Alchemy Portfolio APIs with explicit pagination, partial-failure, privacy, and reconciliation contracts. Use when building wallet portfolio views. Trigger with "Alchemy portfolio", "multi-chain token balances", or "wallet holdings dashboard".
Why this skill is useful
Adds a complete wallet portfolio tracker with executable TypeScript code leveraging Alchemy's Enhanced APIs for fetching token balances, NFTs, and transaction history.
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 Multi-Chain Portfolio Workflow Overview Design a multi-chain holdings workflow on Alchemy Portfolio APIs with explicit pagination, partial-failure, privacy, and reconciliation contracts. 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 Portfolio APIs aggregate fungible tokens and NFTs across requested networks. Multi-network fanout can return HTTP 200 while reporting error.partialErrors; failed networks can be absent from pagination. Therefore HTTP success is not completeness, and retries for failed networks begin as fresh bounded requests rather than continuing the successful-network cursor. Authentication Use an application API key appropriate to Portfolio APIs and keep it in the approved server boundary. Wallet addresses are personal or customer-linked data when the product context makes them identifiable; apply the declared notice, consent, retention, and logging policy. Instructions 1. Define the supported network set, address source, freshness SLO, display currency, pagination limit, and completeness status shown to users. 2. Confirm every requested Portfolio network in current documentation and validate each address before provider access. 3. Call the appropriate Portfolio token or NFT endpoint through a response-validating adapter; retain the request's network set with the result. 4. Persist successful network pages and surface top-level error.partialErrors as named unavailable networks rather than dropping them. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-core-workflow-a