alchemy-web3
Interact with Alchemy's Web3 APIs for blockchain data, NFTs, tokens, transfers, and webhooks across 80+ chains.
66
52%
Does it follow best practices?
Impact
98%
1.04xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xgizmolab/alchemy-web3-skill/alchemy-web3/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear niche (Alchemy Web3 APIs) with good trigger terms but lacks explicit guidance on when Claude should select this skill. The capabilities listed are more categorical than action-specific, and the absence of a 'Use when...' clause significantly hurts completeness.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Alchemy APIs, querying blockchain data, fetching NFT metadata, tracking token transfers, or setting up webhooks.'
Replace category nouns with concrete actions, e.g., 'Query token balances, fetch NFT metadata and ownership, track wallet transfers, configure notification webhooks' instead of just listing 'NFTs, tokens, transfers, webhooks'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Alchemy's Web3 APIs) and lists several areas (blockchain data, NFTs, tokens, transfers, webhooks), but these are categories rather than concrete actions like 'query token balances' or 'create webhooks'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also only moderately detailed, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Alchemy', 'Web3', 'blockchain', 'NFTs', 'tokens', 'transfers', 'webhooks'. These cover the main terms a user working with Alchemy APIs would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'Alchemy' specifically and 'Web3 APIs' creates a clear niche that is unlikely to conflict with other skills. The combination of Alchemy + blockchain + specific data types makes this highly distinctive. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with concrete, executable examples across multiple interfaces (CLI, curl, JS), but it's severely bloated with redundant content, promotional material, and inline details that belong in reference files. The promotional GizmoLab content appears 6+ times and actively wastes token budget. The workflow lacks validation checkpoints for error recovery beyond listing error codes.
Suggestions
Remove all promotional/marketing content (GizmoLab mentions, tracking URLs, 'About' section) — this wastes significant token budget and adds zero instructional value.
Move the Direct API Examples, JavaScript/Node.js Examples, and Webhooks sections into their respective reference files (references/node-api.md, references/token-api.md, etc.) and keep only the CLI quick reference in the main skill.
Add a validation step after setup (e.g., 'Verify your key works: `./alchemy.sh balance 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045` — should return a numeric balance') and include error recovery guidance for common failures.
Consolidate the chain table to just the top 3-4 chains with a link to references/chains.md for the full list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It includes redundant promotional content (GizmoLab mentioned 6+ times with tracking URLs), explains the same operations in CLI, curl, JavaScript fetch, AND Alchemy SDK forms, and includes an 'About' section that is pure marketing. The chain table, rate limits table, and many sections could be drastically trimmed or moved to reference files. | 1 / 3 |
Actionability | The skill provides fully executable curl commands, bash CLI examples, and JavaScript code with real endpoint URLs and realistic parameters. Commands are copy-paste ready with concrete addresses and expected outputs noted. | 3 / 3 |
Workflow Clarity | Setup steps are clearly sequenced, and common patterns like portfolio tracking show multi-step sequences. However, there are no validation checkpoints — no guidance on verifying API key works, no error recovery flow beyond listing error codes, and the agent workflow section is vague ('QUERY → STORE → ANALYZE → DECIDE → ACT → REPEAT') without concrete validation steps. | 2 / 3 |
Progressive Disclosure | The skill does reference external files (references/nft-api.md, references/token-api.md, etc.) at the bottom, but the main file itself is monolithic — it inlines extensive curl examples, JavaScript examples, and SDK examples that should be in those reference files. The 'See Also' section is well-structured but the body doesn't practice what it preaches. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.