AF polymarket-market-movers
Polymarket market probability movement detection. Real-time scanning of probability fluctuations in prediction markets to help users capture "information arbitrage" windows — markets often show significant probability lag within seconds to minutes after news releases, and movements are the most direct signal. Trigger words: probability movement, market volatility, significant changes, which markets are moving, movement detection, movement alerts, market pulse, prob radar, price spike, market movement, which market is most active, where's the volatility, recent big fluctuations. Must trigger when user asks "which markets are fluctuating dramatically right now", "largest probability changes in the past hour", "help me set up a movement alert". Note: Do NOT trigger when user is only asking about current odds for a specific market (without "fluctuation/change/movement" intent), or specifically asking about whale trades or smart money address analysis.
As a process F 52/100 · Will not run — References files that are not bundled: URL
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: URL
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: URL
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (polymarket-market-movers) differs from the folder (polymarket-predictradar-market-movers-skills)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 7 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1392 tokens
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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)
- +3Description length 961: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.