scanning-market-movers
Detect significant price movements and unusual volume across crypto markets. Calculates significance scores combining price change, volume ratio, and market cap. Use when tracking market movers, finding gainers/losers, or detecting volume spikes. Trigger with phrases like "scan market movers", "top gainers", "biggest losers", "volume spikes", "what's moving", "find pumps", or "market scan".
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that excels across all dimensions. It provides specific capabilities (price movement detection, volume analysis, significance scoring), explicit trigger guidance with natural user phrases, and a clear 'Use when' clause. The crypto market scanning niche is well-defined and distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: detect price movements, detect unusual volume, calculate significance scores combining price change/volume ratio/market cap. These are specific, measurable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (detect price movements, unusual volume, calculate significance scores) and 'when' (explicit 'Use when...' clause plus a dedicated 'Trigger with phrases like...' section with concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'scan market movers', 'top gainers', 'biggest losers', 'volume spikes', 'what's moving', 'find pumps', 'market scan'. These are phrases users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to crypto market scanning with distinct triggers like 'volume spikes', 'find pumps', 'market scan'. The crypto-specific domain plus the focus on price movements and volume analysis creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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—every instruction is a concrete, executable command. The progressive disclosure is good with clear references to supporting files. Main weaknesses are minor verbosity (redundant inline comments explaining numeric values, slightly large output example) and the lack of validation steps for verifying prerequisites and API connectivity before running scans.
Suggestions
Add a validation step at the beginning to verify the tracking-crypto-prices dependency is installed and API is reachable (e.g., a --check or --health flag), which would improve workflow clarity.
Remove the inline comments that explain obvious numeric values (e.g., '# 1000000000 = $1B cap') since Claude can interpret these, and trim the output example to fewer rows to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary elements: inline comments explaining obvious numeric values (e.g., '# 1000000000 = $1B cap'), the overview paragraph restates what the description already covers, and the large output example could be trimmed. The error handling table and examples sections are useful but slightly verbose. | 2 / 3 |
Actionability | Every instruction provides a concrete, copy-paste-ready bash command with specific flags and values. The CLI interface is well-documented with real flag names, multiple usage patterns, and clear output format. Users know exactly what to run and what to expect. | 3 / 3 |
Workflow Clarity | Steps are clearly listed and sequenced, but there are no validation checkpoints or feedback loops. For a scanning tool that depends on external APIs and a prerequisite plugin, there's no step to verify the plugin is installed, no way to validate API connectivity before scanning, and no guidance on what to do if partial results are returned beyond 'normal, proceed.' | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, and appropriately references external files for detailed content (implementation.md, errors.md, examples.md). References are one level deep and clearly signaled with full paths. The main file stays focused on quick-start usage patterns. | 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
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.