alchemy-web3
Interact with Alchemy's Web3 APIs for blockchain data, NFTs, tokens, transfers, and webhooks across 80+ chains.
74
Quality
63%
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 effectively identifies a clear niche (Alchemy Web3 APIs) with good domain-specific trigger terms, making it distinctive. However, it lacks explicit 'Use when...' guidance and could be more specific about concrete actions beyond 'Interact with'. The description would benefit significantly from adding trigger conditions.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about Alchemy APIs, blockchain queries, NFT metadata, token balances, or setting up webhooks'
Replace 'Interact with' with specific action verbs like 'Query blockchain data, fetch NFT metadata, track token transfers, configure webhooks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Alchemy's Web3 APIs) and lists several action areas (blockchain data, NFTs, tokens, transfers, webhooks), but uses 'Interact with' which is somewhat vague rather than listing concrete actions like 'fetch', 'query', 'create', or 'monitor'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Alchemy', 'Web3', 'blockchain', 'NFTs', 'tokens', 'transfers', 'webhooks'. These cover common variations of what users working with blockchain APIs would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Alchemy's APIs specifically, with distinct blockchain/Web3 terminology. Unlikely to conflict with other skills due to the specific platform name and domain-specific terms like NFTs, webhooks, and '80+ chains'. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, actionable API reference skill with excellent code examples across multiple languages and use cases. The main weaknesses are promotional content that wastes tokens and missing error handling/validation workflows for production use. The structure and progressive disclosure are well-executed.
Suggestions
Remove all GizmoLab promotional content and marketing links - they don't help Claude execute tasks and waste context window space
Add a troubleshooting/validation section showing how to verify API key works, handle rate limits gracefully, and retry failed requests
Add validation step after setup: 'Test your key: ./alchemy.sh balance 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 should return a balance'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes promotional content (GizmoLab mentions, marketing links with UTM parameters) that doesn't serve Claude's task execution. The 'About' section is pure marketing filler. | 2 / 3 |
Actionability | Excellent executable examples throughout - curl commands, bash scripts, JavaScript code with both fetch and SDK approaches. All examples are copy-paste ready with real addresses and complete syntax. | 3 / 3 |
Workflow Clarity | Setup steps are clear, and common patterns section shows multi-step workflows. However, there's no validation/error recovery guidance - what to do when rate limited, how to verify API key works, or how to handle failed requests in batch operations. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (references/nft-api.md, agent-workflows.md, etc.). The main skill provides quick reference while pointing to detailed docs for deeper dives. | 3 / 3 |
Total | 10 / 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
5342bca
- 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.