exploring-blockchain-data
Process query and analyze blockchain data including blocks, transactions, and smart contracts. Use when querying blockchain data and transactions. Trigger with phrases like "explore blockchain", "query transactions", or "check on-chain data".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/crypto/blockchain-explorer-cli/skills/exploring-blockchain-data/SKILL.mdQuality
Discovery
89%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 a solid description that clearly identifies its domain (blockchain data) and provides explicit trigger guidance with natural user phrases. Its main weakness is that the capability verbs ('process', 'analyze') are somewhat generic—more specific actions would strengthen it. Overall it performs well for skill selection purposes.
Suggestions
Replace generic verbs like 'process' and 'analyze' with more specific actions such as 'decode transaction logs', 'inspect smart contract state', 'trace token transfers', or 'look up block details' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blockchain) and some actions (process query, analyze), and mentions specific data types (blocks, transactions, smart contracts), but the actions themselves are somewhat generic ('process', 'analyze') rather than listing concrete operations like 'decode transaction logs', 'inspect contract state', or 'trace token transfers'. | 2 / 3 |
Completeness | Clearly answers both 'what' (process query and analyze blockchain data including blocks, transactions, and smart contracts) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' clause providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'explore blockchain', 'query transactions', 'check on-chain data', 'blocks', 'transactions', 'smart contracts', 'blockchain data'. These cover terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Blockchain data querying is a clear niche with distinct triggers like 'on-chain data', 'blockchain', 'transactions', and 'smart contracts'. This is unlikely to conflict with other skills unless there are multiple blockchain-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete CLI commands and good error handling coverage. Its main weaknesses are verbosity (the error table and output descriptions are extensive) and lack of explicit validation checkpoints in the workflow. The content would benefit from trimming redundant descriptions and adding verification steps between operations.
Suggestions
Add a validation step early in the workflow (e.g., 'Run `python blockchain_explorer.py --version` to verify installation, then test API connectivity with `python blockchain_explorer.py block latest`') to establish a feedback loop before complex queries.
Move the detailed error handling table and output format descriptions to a separate reference file (e.g., `references/errors.md` and `references/output-formats.md`) and keep only the 2-3 most common errors inline.
Trim explanatory prose after example commands — the commands and flags are self-documenting enough that sentences like 'Useful for whale watching or due diligence on a wallet' add little value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary verbosity, particularly in the Output section which exhaustively lists every field in every output type, and the Error Handling table which covers many edge cases that could be more concise. The Examples section also includes explanatory prose after each command that could be trimmed. | 2 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready CLI commands with specific flags, real contract addresses (USDC), and clear expected outputs. Each instruction step maps to an executable command with specific syntax. | 3 / 3 |
Workflow Clarity | The instructions are presented as a numbered list of independent commands rather than a coherent multi-step workflow with validation checkpoints. There's no explicit validation/verification step (e.g., confirming API key is working before proceeding, or verifying output correctness). The reference to a 'full four-step implementation workflow' in implementation.md suggests the actual workflow is deferred elsewhere. | 2 / 3 |
Progressive Disclosure | There is one reference to an external file (`references/implementation.md`) for the implementation workflow, which is good. However, the main file is quite long (~100+ lines of content) with extensive error handling tables and output descriptions that could be split into reference files. The Resources section at the end is helpful but the overall document could benefit from moving the error table and detailed output descriptions to separate files. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.