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".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 solid skill description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond general tracking and monitoring. The distinct cryptocurrency whale-tracking niche makes it highly distinguishable from other skills.
Suggestions
Add more specific concrete actions such as 'alert on transfers exceeding a threshold', 'identify wallet accumulation/distribution patterns', or 'summarize exchange deposit/withdrawal flows' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (cryptocurrency transactions, whale wallets) and some actions (track, monitor), but doesn't list multiple concrete specific actions beyond tracking/monitoring. It lacks specifics like 'alert on transfers above X', 'identify accumulation patterns', or 'generate flow reports'. | 2 / 3 |
Completeness | Clearly answers both 'what' (track large cryptocurrency transactions and whale wallet movements in real-time) and 'when' (explicit 'Use when' clause with trigger scenarios plus a 'Trigger with phrases like' section providing concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'track whales', 'monitor large transfers', 'check whale activity', 'exchange inflows', 'watch wallet', 'whale wallet movements', 'exchange flows'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on cryptocurrency whale tracking and large transaction monitoring. The specific domain terms like 'whale', 'exchange inflows', and 'large transfers' are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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-structured skill with strong actionability and good progressive disclosure. The main weaknesses are some unnecessary explanatory content that Claude wouldn't need (basic trading concepts) and a lack of inline validation steps, with error handling entirely deferred to an external reference file. The command examples are concrete and executable, making this practically useful.
Suggestions
Add a brief validation step after Step 2, such as 'Run `python whale_monitor.py recent` first to verify API connectivity and script functionality before applying filters.'
Remove the explanations of transaction types and flow analysis meanings (DEPOSIT = selling pressure, etc.) as Claude can infer these from context, or move them to the references file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation Claude would already know (e.g., explaining what DEPOSIT/WITHDRAWAL/TRANSFER mean, explaining that net positive flow = selling pressure). The inline comments like '# 10000000 = 10M limit' are redundant given the context already states '$10M+ only'. Some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands with specific flags and arguments. Commands are copy-paste ready, cover multiple use cases, and include concrete wallet address examples and flag combinations. The skill delegates to a script but gives clear, specific invocations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (navigate, choose command, interpret), but there are no validation checkpoints. For a monitoring tool that involves API calls, there's no guidance on verifying the script works, checking API key validity, or confirming output correctness. Error handling is entirely deferred to an external file rather than providing inline validation steps. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear table of contents, concise overview in the main file, and appropriate one-level-deep references to external files (errors.md, examples.md, implementation.md). Content is appropriately split between the main skill file and reference materials. | 3 / 3 |
Total | 10 / 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 | |
- Commit
c8a915c
- 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.