analyzing-on-chain-data
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-on-chain-dataProcess 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".
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
35%This skill provides a structural framework but lacks concrete, executable guidance. The content over-relies on external references without providing sufficient actionable content in the main file. The instructions describe what to do at a high level but don't show how to do it with actual code or commands.
Suggestions
Add at least one complete, executable code example showing how to query blockchain data (e.g., fetching ETH balance or token transfers using ethers.js or web3.py)
Include a concrete example of the Bash(crypto:onchain-*) command syntax with actual parameters and expected output
Add validation steps between setup and execution phases (e.g., 'Verify connection: run `curl $RPC_ENDPOINT -X POST...` and confirm response')
Remove the generic overview sentence and trim prerequisites to only non-obvious requirements
| 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 instructions are reasonably efficient 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. Everything actionable is deferred to external files. | 1 / 3 |
Workflow Clarity | Steps are numbered but lack validation checkpoints. No feedback loops for error recovery. The workflow jumps from setup to execution without clear verification that connections work before proceeding. | 2 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md) but the main skill file is too sparse - it defers almost all useful content to other files while providing little actionable guidance itself. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
67%This description has a solid structure with explicit 'Use when' and trigger phrase guidance, which is good practice. 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 financial market skills. The triggers are somewhat broad and could conflict with general crypto price checking or trading skills. | 2 / 3 |
Total | 9 / 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.