AF 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".
As a process F 49/100 · Will not run — References files that are not bundled: scripts/scanner.py, scripts/analyzer.py, scripts/filters.py
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/scanner.py - warning
missing-refreference to a missing file: scripts/analyzer.py - warning
missing-refreference to a missing file: scripts/filters.py - warning
missing-refreference to a missing file: scripts/scorers.py - warning
missing-refreference to a missing file: scripts/formatters.py
Process rating: all ten parameters 49/100
- 0Tools and files. 5 referenced file(s) missing: scripts/scanner.py, scripts/analyzer.py, scripts/filters.py
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (scanning-market-movers) differs from the folder (scanning-market-movers-ti)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 1925 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 393: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 12 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.