alchemy-api
Wire Alchemy into application code using a standard API key. Covers EVM JSON-RPC, Token API, Transfers API, Prices API, Portfolio API, Simulation, Webhooks, Solana RPC/DAS/Yellowstone gRPC, Sui gRPC, Wallets/Account Kit. For NFT marketplace data, listings, offers, or Seaport fulfillment, use `opensea-api` / `opensea-marketplace`. For live agent work, use `alchemy-cli` or `alchemy-mcp`. For app code without an API key, use `alchemy-agentic-gateway`.
73
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly specifies concrete capabilities, includes abundant natural trigger terms, and explicitly addresses both what the skill does and when to use it. Its strongest feature is the explicit disambiguation from related skills, which dramatically reduces conflict risk in a multi-skill environment. The only minor note is that it lacks a formal 'Use when...' clause, but the opening sentence and boundary conditions effectively serve the same purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: EVM JSON-RPC, Token API, Transfers API, Prices API, Portfolio API, Simulation, Webhooks, Solana RPC/DAS/Yellowstone gRPC, Sui gRPC, Wallets/Account Kit. Also specifies the integration pattern ('using a standard API key'). | 3 / 3 |
Completeness | Clearly answers 'what' (wire Alchemy into application code covering specific APIs) and 'when' (when using a standard API key). It also explicitly delineates boundaries by stating when NOT to use it and which alternative skills to use instead (opensea-api, alchemy-cli, alchemy-mcp, alchemy-agentic-gateway), which serves as strong implicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords users would say: 'Alchemy', 'API key', 'EVM', 'JSON-RPC', 'Token API', 'Webhooks', 'Solana', 'Sui', 'Portfolio', 'Simulation', 'Account Kit'. These are terms developers would naturally use when asking about Alchemy integration. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — explicitly differentiates itself from four related skills (opensea-api, opensea-marketplace, alchemy-cli, alchemy-mcp, alchemy-agentic-gateway) with clear boundary conditions (API key vs no API key, app code vs live agent work, NFT marketplace data). This makes conflict very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that excels at actionability and progressive disclosure. It provides a comprehensive yet navigable guide for Alchemy API integration with executable examples, clear decision trees for scope routing, and well-organized references to deeper content. The main weakness is moderate verbosity in explanatory notes and the CLI bridging section, which could be tightened without losing clarity.
Suggestions
Trim the three blockquote explanations in the CLI bridging section ('Why we persist to .env', 'Why this whole flow works', 'Gotcha') to 1-2 sentences each — Claude can infer the rationale for .env persistence and the flow logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some verbose sections that could be tightened. The CLI bridging section is quite long with extensive explanatory notes ('Why we persist to .env', 'Why this whole flow works', 'Gotcha'), and the scope_out table is exhaustive but includes many entries Claude could look up. The common token addresses and some cheat sheets earn their place, but the overall document could be ~30% shorter. | 2 / 3 |
Actionability | Excellent actionability throughout. The quickstart section provides fully executable curl commands for every major API surface. The CLI bridging script is complete and copy-paste ready with proper error handling. The webhook verification code is executable TypeScript. Base URLs are concrete with exact URL patterns. | 3 / 3 |
Workflow Clarity | The mandatory preflight gate provides a clear decision tree with explicit validation steps (check env var, fallback options in priority order). The CLI bridging flow is sequenced with numbered steps and includes error recovery (the 'Gotcha' about re-running apps select). The 'Do this first' section provides a clear 4-step workflow. Security constraints are explicit (NEVER echo the key). | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a self-contained overview with clear pointers to 90+ reference files organized by product area. The endpoint selector table maps tasks to specific reference files. The skill map section provides a category overview with a pointer to the full index. References are consistently one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- ProjectOpenSea/opensea-skill
- Commit
10f23f8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.