monitoring-whale-activity
Track large cryptocurrency transactions and whale wallet movements in real-time. Use when tracking large holder movements, exchange flows, or wallet activity. Trigger with phrases like "track whales", "monitor large transfers", "check whale activity", "exchange inflows", or "watch wallet".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-whale-activity88
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
89%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 is a well-crafted skill description with strong trigger term coverage and explicit usage guidance. The main weakness is that the capability description could be more specific about concrete actions beyond 'track' and 'monitor'. The description effectively distinguishes itself from general cryptocurrency skills through whale-specific terminology.
Suggestions
Expand specificity by listing concrete actions like 'alert on transfers exceeding thresholds', 'analyze wallet transaction history', 'identify accumulation patterns', or 'track exchange deposit/withdrawal flows'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cryptocurrency transactions, whale wallets) and some actions (track, monitor), but lacks comprehensive specific actions like 'alert on transfers over X', 'analyze wallet history', or 'generate movement reports'. | 2 / 3 |
Completeness | Clearly answers both what (track large cryptocurrency transactions and whale wallet movements) and when (explicit 'Use when...' clause with specific scenarios plus 'Trigger with phrases' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'track whales', 'monitor large transfers', 'check whale activity', 'exchange inflows', 'watch wallet'. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on cryptocurrency whale tracking with unique triggers like 'whale activity', 'exchange inflows' that are unlikely to conflict with general crypto or finance skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and conciseness. Commands are concrete and executable, the structure is logical, and external references are appropriately signaled. The main weakness is the lack of validation steps for operations like adding wallets to watchlists or verifying address formats before tracking.
Suggestions
Add a validation step after watchlist operations (e.g., 'Verify addition: python whale_monitor.py watchlist | grep 0x123...')
Include address format validation guidance before tracking commands to prevent errors with malformed addresses
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, presenting commands directly without explaining what whales are or how blockchains work. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable bash commands with clear flags and options. Commands are copy-paste ready with specific examples like chain filters and minimum value thresholds. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For monitoring operations that could involve tracking incorrect addresses, there's no verification step to confirm watchlist additions or validate address formats before tracking. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, then detailed commands, then examples. Appropriately references external files (errors.md, examples.md) for deeper content without nesting multiple levels deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| 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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.