CtrlK
BlogDocsLog inGet started
Tessl Logo

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

56

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with concrete, copy-paste-ready commands and a clean section structure, but it is held back by redundant inline examples that duplicate bundled reference files and by a lack of validation checkpoints in its workflows.

Suggestions

Move the duplicated example/error content into the existing examples.md and errors.md and link them from the body instead of inlining, so progressive disclosure is appropriately split.

Trim the Examples section or fold it into the referenced examples.md to reduce redundancy with the Instructions list.

Add explicit validation/verification steps where workflows chain multiple commands (e.g., confirm a protocol slug exists before pulling fees) to raise workflow clarity.

DimensionReasoningScore

Conciseness

The body is action-oriented and avoids explaining basic DeFi concepts, but the Examples section largely restates the Instructions and duplicates the bundled examples.md, so it is 'mostly efficient but could be tightened' rather than the lean level 3.

2 / 3

Actionability

It provides exact, executable CLI commands with concrete flags (e.g., 'python onchain_analytics.py protocols --category lending --sort tvl_to_mcap') and copy-paste-ready bash examples, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

A numbered command sequence and example workflows are present, but there are no validation or checkpoint steps — it reads as a command menu rather than a checkpointed process, so it sits at 'steps listed but validation gaps' rather than level 3.

2 / 3

Progressive Disclosure

It makes one real one-level reference (implementation.md) but leaves examples.md and errors.md unlinked while duplicating their content inline, fitting 'some structure but content that should be separate is inline' rather than the well-split level 3.

2 / 3

Total

9

/

12

Passed

Description

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 both what the skill does and when to use it with explicit triggers, but a garbled opening verb ('Process perform') and incomplete trigger-term coverage keep it from being fully specific or fully distinctive.

Suggestions

Fix the broken opening verb (e.g., 'Process and perform on-chain analysis' or just 'Perform on-chain analysis') so the lead action is grammatical and concrete.

Broaden trigger terms to include natural variations users would say, such as 'DeFi', 'TVL', 'track whales', or 'token flow'.

Tighten the niche so it cannot be confused with general crypto/market skills — lead with the distinctive on-chain/whale-tracking framing rather than the generic 'monitor market'.

DimensionReasoningScore

Specificity

Names concrete areas ('whale tracking, token flows, and network activity') but the lead verb is broken ('Process perform on-chain analysis') and the actions are not comprehensive, matching the 'names domain and some actions' anchor rather than the multiple-specific-actions level 3.

2 / 3

Completeness

It explicitly answers both what ('perform on-chain analysis including whale tracking, token flows, and network activity') and when ('Use when performing crypto analysis' plus explicit trigger phrases), satisfying the level-3 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Phrases like 'analyze crypto', 'check blockchain', and 'monitor market' are reasonably natural, but coverage is incomplete — common variations such as DeFi, TVL, 'track whales', or 'token flow' are missing, so it lands at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The on-chain/whale/token-flow niche is fairly distinct, but generic triggers like 'monitor market' and 'crypto analysis' could overlap with general crypto or market-monitoring skills, so it does not reach the clear-niche level 3.

2 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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