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".
80
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/crypto/whale-alert-monitor/skills/monitoring-whale-activity/SKILL.mdQuality
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 'when to use' guidance. Its main weakness is that the 'what it does' portion could be more specific about concrete capabilities beyond just tracking/monitoring (e.g., does it generate alerts, produce reports, compare historical patterns?). The explicit trigger phrases section is a strong differentiator.
Suggestions
Add more specific concrete actions beyond 'track' and 'monitor' — e.g., 'Alerts on transactions above configurable thresholds, identifies accumulation/distribution patterns, summarizes exchange net flows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cryptocurrency transactions, whale wallets) and some actions (track, monitor), but doesn't list multiple concrete specific actions beyond tracking/monitoring. It could be more specific about what outputs or analyses it provides (e.g., alert thresholds, historical analysis, portfolio breakdowns). | 2 / 3 |
Completeness | Clearly answers both 'what' (track large cryptocurrency transactions and whale wallet movements in real-time) and 'when' (explicit 'Use when' clause plus a 'Trigger with phrases like' section providing concrete trigger 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', 'exchange flows', 'whale wallet movements'. These are terms crypto users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on large crypto transactions and whale tracking. The specific terminology (whale, exchange inflows, large transfers) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable CLI commands for whale monitoring with good examples and well-structured output descriptions. Its main weaknesses are the lack of validation checkpoints (e.g., verifying API key setup, confirming script availability) and some redundancy between inline examples and the referenced examples.md file. The content is generally well-organized but could be tighter.
Suggestions
Add a validation step after prerequisites (e.g., 'Verify setup: python whale_monitor.py --help should show available commands') to confirm the environment is ready.
Either move the detailed examples to the referenced examples.md and keep only one quick example inline, or remove the reference to examples.md to avoid redundancy.
Remove the inline comments that restate obvious information (e.g., '# 10000000 = 10M limit') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like the table of contents links for a document this size, and some comments that restate obvious things (e.g., '10000000: $10M+ only'). The overview partially restates the description. Could be tightened. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready bash commands with specific flags and arguments. Multiple executable examples cover different use cases, and the CLI interface is clearly documented with real command patterns. | 3 / 3 |
Workflow Clarity | Steps are listed and sequenced clearly, but there are no validation checkpoints. There's no guidance on verifying the script exists, confirming API connectivity, or validating output correctness. The 'Interpret Results' section helps but lacks a feedback loop for when things go wrong. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md, implementation.md) are well-signaled and one level deep, which is good. However, no bundle files were provided, so we can't verify these references actually exist. The main content is reasonably structured but the inline examples section is somewhat long when examples.md is also referenced. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.