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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-on-chain-data59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has good structural completeness with explicit 'Use when' and trigger phrase guidance, which is commendable. However, the capabilities listed are somewhat high-level categories rather than concrete actions, and the trigger terms could be more comprehensive to cover the full range of on-chain analysis terminology users might employ.
Suggestions
Add more specific concrete actions like 'track wallet addresses', 'analyze transaction histories', 'identify large transfers', or 'monitor smart contract interactions' to improve specificity.
Expand trigger terms to include common variations like 'whale alerts', 'token movements', 'wallet tracking', 'on-chain data', 'transaction analysis', or specific blockchain names (Ethereum, Solana, etc.).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (on-chain analysis) and lists some actions (whale tracking, token flows, network activity), but these are somewhat high-level categories rather than concrete specific actions like 'track wallet addresses' or 'calculate token transfer volumes'. | 2 / 3 |
Completeness | Clearly answers both what (on-chain analysis including whale tracking, token flows, network activity) and when (explicit 'Use when' clause and 'Trigger with phrases' providing specific trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords ('analyze crypto', 'check blockchain', 'monitor market') but missing common variations users might say like 'wallet tracking', 'token movements', 'on-chain data', 'whale alerts', or specific blockchain names. | 2 / 3 |
Distinctiveness Conflict Risk | The crypto/blockchain focus provides some distinctiveness, but 'monitor market' is generic and could overlap with traditional finance skills. The triggers are somewhat broad and could conflict with general crypto price checking or trading skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a skeleton that defers nearly all actionable content to external reference files. It lacks concrete code examples, executable commands, or specific API usage patterns. The workflow has structural issues (duplicate numbered lists) and missing validation steps for operations involving external APIs and blockchain queries.
Suggestions
Add at least one complete, executable code example showing how to query blockchain data or fetch market prices using the mentioned tools (ethers.js, web3.py)
Fix the duplicate numbered lists (1-5, 1-5) by combining into a single coherent workflow with explicit validation checkpoints after API connections
Replace vague instructions like 'Use Bash(crypto:onchain-*) to execute crypto data queries' with actual command examples showing specific queries
Remove the generic overview sentence and prerequisites that Claude already understands (e.g., 'Understanding of blockchain concepts')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like 'This skill provides automated assistance for the described functionality' and explains prerequisites Claude would know. The instructions are reasonably compact but could be tighter. | 2 / 3 |
Actionability | No executable code examples provided. Instructions are vague ('Use Bash(crypto:onchain-*) to execute crypto data queries') without showing actual commands, API calls, or concrete implementation. References external files for all details. | 1 / 3 |
Workflow Clarity | Steps are numbered but lack validation checkpoints. Two separate numbered lists (1-5, then 1-5 again) create confusion. No feedback loops for error recovery despite dealing with external APIs and blockchain queries. | 2 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md), but the main content is too thin - it defers almost everything to external files while providing minimal actionable content in the skill itself. | 2 / 3 |
Total | 7 / 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 | |
- 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.