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".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, highly actionable, and token-efficient, with concrete executable commands, a clear error-handling table, and a single well-signaled reference for the detailed workflow. It is a strong, ready-to-use skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — a one-sentence overview, ten concrete CLI invocations, and tight examples with no concept-explanation padding (no 'what is TVL/DeFi' bloat), matching the score-3 anchor.	3 / 3
Actionability	It provides fully executable commands with exact flags and copy-paste-ready examples (e.g. 'python onchain_analytics.py yields --min-tvl 10000000 --chain ethereum --limit 50'), matching the score-3 anchor.	3 / 3
Workflow Clarity	The ten numbered steps are unambiguous and the operations are independent read-only queries rather than a destructive/batch pipeline, so the missing-validation cap does not apply; the Error Handling table supplies recovery guidance for each failure mode.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that points one level deep to references/implementation.md for the full workflow, with real, well-organized bundle files in references/ and scripts/, matching the score-3 anchor for clear navigation.	3 / 3
	Total	12 / 12 Passed

Description

77%Weight 40%Scale 1-3

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 what and when with explicit triggers and concrete actions, but the trigger terms are somewhat generic and incomplete, and the opening 'Process perform' phrasing is grammatically broken. Distinctiveness is decent but weakened by broad wording.

Suggestions

Fix the broken 'Process perform on-chain analysis' opener to a clean third-person verb phrase such as 'Perform on-chain analysis including whale tracking, token flows, and network activity.'

Replace the generic 'monitor market' trigger with on-chain-specific natural phrases users would actually say, e.g. 'track whale wallets', 'trace token flows', or 'analyze on-chain data'.

Tighten the 'when' clause to reference the specific domain (on-chain/blockchain analytics) rather than the broad 'performing crypto analysis' to reduce overlap with general crypto skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('whale tracking, token flows, and network activity') rather than vague language, matching the score-3 anchor; the duplicated 'Process perform' phrasing is grammatically awkward but still names specific capabilities.	3 / 3
Completeness	It answers both 'what' (on-chain analysis covering whale tracking, token flows, network activity) and 'when' via an explicit 'Use when performing crypto analysis' clause plus dedicated trigger phrases, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Trigger phrases ('analyze crypto', 'check blockchain', 'monitor market') are plausible but incomplete and partly generic — 'monitor market' is broad and not on-chain-specific, and common natural variations like 'track whales' or 'on-chain data' are missing.	2 / 3
Distinctiveness Conflict Risk	The on-chain niche is reasonably distinct, but 'performing crypto analysis' and 'monitor market' are broad enough to overlap with general crypto/market skills, so it does not fully reach the clear-niche score-3 anchor.	2 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/crypto/on-chain-analytics/skills/analyzing-on-chain-data/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.