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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill scanning-market-movers84
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
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 an excellent skill description that hits all the key criteria. It provides specific capabilities (price movement detection, significance scoring), clear use cases, and comprehensive trigger terms that users would naturally use. The crypto-specific focus makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Detect significant price movements', 'unusual volume', 'Calculates significance scores combining price change, volume ratio, and market cap'. These are specific, measurable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (detect price movements, calculate significance scores) AND when ('Use when tracking market movers, finding gainers/losers, or detecting volume spikes') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'scan market movers', 'top gainers', 'biggest losers', 'volume spikes', 'what's moving', 'find pumps', 'market scan'. These are terms users would naturally say when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with crypto-specific terminology ('pumps', 'market cap', 'volume spikes') and clear niche focus on crypto market scanning. Unlikely to conflict with general finance or other trading skills due to specific trigger terms. | 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 solid, actionable skill with clear executable commands and good progressive disclosure through external references. The main weaknesses are some verbosity in the overview section and missing validation checkpoints for error scenarios like rate limiting or dependency failures. The significance score explanation and configuration examples are well done.
Suggestions
Add explicit validation steps after running scans, such as checking for 'Partial results' warnings or verifying dependency availability before proceeding
Trim the Overview section - the 'Key Features' list largely duplicates information from the skill description and could be removed or condensed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity like the 'Key Features' bullet list that restates what the description already covers, and the overview section could be tighter. The output examples are helpful but lengthy. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear flags and options. Code examples are copy-paste ready with specific parameters, and the configuration YAML is complete and usable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints or error recovery feedback loops. For a scanning operation that could fail due to rate limits or missing dependencies, explicit validation steps would improve reliability. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate references to external files (errors.md, examples.md), and a clean file table. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 10 / 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.