exploring-blockchain-data
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exploring-blockchain-dataProcess 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
22%This skill is too abstract and defers nearly all actionable content to external reference files. The main body lacks executable code examples, has poorly structured workflows with duplicate numbering, and includes verbose boilerplate that doesn't add value. The skill tells Claude what to do conceptually but doesn't show how to do it concretely.
Suggestions
Add at least one executable code example showing how to query blockchain data (e.g., using ethers.js or web3.py with actual API calls)
Fix the duplicate numbered lists and add explicit validation checkpoints (e.g., 'Verify API response status before processing')
Remove the generic overview sentence and trim prerequisites to only non-obvious requirements
Include at least one inline example of the Bash command pattern mentioned (crypto:explorer-*) with expected output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like 'This skill provides automated assistance for the described functionality' and verbose prerequisites that Claude would already understand. The output section lists many items that could be more concise. | 2 / 3 |
Actionability | No executable code examples provided. Instructions are vague ('Use Bash(crypto:explorer-*) to execute crypto data queries') without showing actual commands or code. References external files for all concrete implementation details. | 1 / 3 |
Workflow Clarity | Steps are listed but poorly organized (two separate numbered lists starting at 1). No validation checkpoints, no error recovery flow, and critical details are deferred to external files. Missing feedback loops for API connectivity testing. | 1 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md), but the main content is too thin - it defers almost all actionable content to other files while keeping verbose boilerplate inline. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a solid skill description that clearly establishes its blockchain-focused domain and provides explicit trigger guidance. The main weakness is that the capability descriptions are somewhat generic ('process', 'analyze') rather than listing specific concrete actions. The trigger terms and explicit 'Use when' clause make it easy for Claude to identify when to select this skill.
Suggestions
Replace generic verbs like 'process' and 'analyze' with more specific actions such as 'decode transaction hashes', 'inspect block headers', 'read smart contract state', or 'trace token transfers'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blockchain) and lists some actions ('query', 'analyze') with objects ('blocks, transactions, smart contracts'), but the actions are somewhat generic rather than concrete specific operations like 'decode transaction hashes' 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 ('Use when querying blockchain data and transactions') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'explore blockchain', 'query transactions', 'check on-chain data', plus implicit terms like 'blocks', 'transactions', 'smart contracts'. These cover common user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Blockchain data analysis is a clear niche with distinct terminology ('blockchain', 'on-chain data', 'smart contracts', 'transactions') that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
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.