alchemy-web3

Interact with Alchemy's Web3 APIs for blockchain data, NFTs, tokens, transfers, and webhooks across 80+ chains.

1.04x

Quality

63%

Does it follow best practices?

Impact

98%

1.04x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xgizmolab/alchemy-web3-skill/alchemy-web3/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a rich, actionable command and API reference with concrete examples, but it is over-long for inline use, relies on bundle files (scripts/, references/) that are absent, and offers workflows without validation checkpoints.

Suggestions

Ship the referenced bundle files (`scripts/alchemy.sh`, `references/nft-api.md`, `references/token-api.md`, `references/node-api.md`, `references/chains.md`, `references/agent-workflows.md`) or remove the broken references from SKILL.md.

Move the bulk of the inline curl/JS/SDK API examples into the referenced `references/*.md` files and keep only a concise quick-start in SKILL.md to improve both conciseness and progressive disclosure.

Trim the promotional "About"/GizmoLab marketing sections and UTM-laden callouts from the skill body to reduce token cost.

Add explicit validation/error-handling checkpoints to the multi-step patterns (e.g., verify a response `error` field before acting on results) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~390-line body is mostly efficient (CLI command tables, terse curl payloads) but carries notable padding: a promotional "About" section with UTM links, repeated marketing callouts, and inline explanations of concepts (JSON-RPC, fetch) Claude already knows.	3 / 5
Actionability	Provides copy-paste-ready CLI commands and full curl/JS/SDK examples covering common cases, but the referenced `scripts/alchemy.sh` and `references/*.md` bundle files do not exist, so several examples are not actually executable in-bundle.	4 / 5
Workflow Clarity	"Common Patterns" lists rough command sequences (e.g., Portfolio Tracker) and a multi-chain loop, but workflows lack explicit validation checkpoints or feedback loops; steps are present yet checkpoints are only implicit.	3 / 5
Progressive Disclosure	A "See Also" section signals one-level-deep references, but the referenced `references/` files are missing (broken links) and large API-reference blocks (curl, JS, SDK) are inlined in SKILL.md rather than split into separate files.	3 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and distinctive, clearly scoping a vendor-specific Web3 API skill with concrete capability areas. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness.

Suggestions

Add an explicit "Use when..." clause naming natural triggers (e.g., "Use when querying on-chain data, NFTs, token balances, transfers, or setting up webhooks across EVM and Solana chains").

Include a few user-natural synonyms/extensions such as "crypto", "wallet", "ETH balance", and "on-chain" to broaden trigger-term coverage.

Replace the single verb "Interact" with more concrete actions (e.g., "Query balances, fetch NFTs, list token holdings, and read asset transfers") to lift specificity toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain (Alchemy Web3 APIs) and five concrete capability areas ("blockchain data, NFTs, tokens, transfers, and webhooks"), but uses a single verb ("Interact") rather than enumerating discrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Provides a clear "what" but has no explicit "Use when..." / "when" trigger clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural user terms ("blockchain data, NFTs, tokens, transfers, webhooks") but misses common synonyms and extensions users actually say ("crypto", "wallet", "ETH balance", "on-chain").	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to a named vendor's API ("Alchemy's Web3 APIs ... across 80+ chains"), a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 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
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	12 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xgizmolab/alchemy-web3-skill/alchemy-web3/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.