analyzing-on-chain-data
Process perform on-chain analysis including whale tracking, token flows, and network activity. Use when performing crypto analysis. Trigger with phrases like "analyze crypto", "check blockchain", or "monitor market".
71
66%
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/on-chain-analytics/skills/analyzing-on-chain-data/SKILL.mdQuality
Discovery
67%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 covers the basics with explicit 'what' and 'when' clauses, which is good for completeness. However, the capabilities listed are more like high-level categories than concrete actions, and the trigger terms are somewhat generic, risking overlap with other crypto or market-related skills. The description would benefit from more specific actions and more distinctive trigger terms.
Suggestions
Add more specific concrete actions like 'track whale wallet movements', 'map token transfer flows between addresses', 'analyze network transaction volume and gas fees' instead of broad subcategories.
Expand trigger terms with more natural variations users would say, such as 'whale alert', 'token transfers', 'wallet activity', 'on-chain data', 'blockchain transactions', and specific chain names like 'Ethereum', 'Solana'.
Narrow the trigger 'monitor market' to something more distinctive like 'monitor blockchain network activity' to reduce conflict risk with general financial market skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (on-chain analysis) and lists some actions (whale tracking, token flows, network activity), but these are more like subcategories than concrete specific actions. It doesn't detail what specific operations are performed (e.g., 'track wallet addresses', 'visualize token transfer graphs'). | 2 / 3 |
Completeness | Explicitly answers both 'what' (on-chain analysis including whale tracking, token flows, network activity) and 'when' (Use when performing crypto analysis, with explicit trigger phrases). The 'Use when' and 'Trigger with' clauses are present. | 3 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases like 'analyze crypto', 'check blockchain', and 'monitor market', but misses many natural variations users might say such as 'whale alert', 'token transfers', 'on-chain data', 'wallet tracking', 'blockchain explorer', or specific chain names. | 2 / 3 |
Distinctiveness Conflict Risk | The description is somewhat specific to on-chain/blockchain analysis, but the broad trigger 'monitor market' could overlap with traditional financial market monitoring skills. 'Analyze crypto' is also fairly broad and could conflict with crypto trading or portfolio skills. | 2 / 3 |
Total | 9 / 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.
The skill provides highly actionable CLI commands with good examples and a comprehensive error handling table, making it practically useful. However, it suffers from moderate verbosity (explaining DeFi concepts, lengthy output descriptions) and lacks a clear multi-step workflow with validation checkpoints—the actual workflow is deferred to an external file. The content would benefit from trimming explanatory text and either inlining the workflow with validation steps or better structuring the progressive disclosure.
Suggestions
Remove the overview paragraph's explanation of target audiences and DeFi concepts—Claude already knows these. Replace with a one-line purpose statement.
Either inline the 'four-step implementation workflow' from implementation.md with explicit validation checkpoints, or restructure the numbered instructions into a clear sequential workflow with verification steps between stages.
Move the detailed error handling table and output format descriptions to a reference file (e.g., references/errors.md) and keep only the 2-3 most common errors inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview paragraph explains DeFi concepts and target audiences that Claude already understands. The error handling table and output section are thorough but somewhat verbose—several entries could be condensed. However, the instructions and examples themselves are reasonably efficient. | 2 / 3 |
Actionability | Every instruction is a concrete, copy-paste-ready CLI command with specific flags and arguments. The examples section provides realistic multi-command workflows with clear explanations of what each produces. The error handling table maps specific errors to specific solutions. | 3 / 3 |
Workflow Clarity | The instructions are a numbered list of independent commands rather than a coherent multi-step workflow with validation checkpoints. There's no explicit validation step or feedback loop—the reference to a 'full four-step implementation workflow' in implementation.md suggests the actual workflow lives elsewhere, leaving this file without clear sequencing or verification steps. | 2 / 3 |
Progressive Disclosure | There is one reference to an external implementation.md file for the full workflow, which is good. However, the main file is quite long with detailed error handling tables and extensive output descriptions that could be split into reference files. The resources section is well-organized but the body content could benefit from better separation of overview vs. reference material. | 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.