AC paradex-market-analyst
Technical analysis, market screening, and regime classification for Paradex perpetual futures markets. Computes indicators (RSI, MACD, Bollinger Bands, ATR, VWAP) from kline data, scans funding rates for arbitrage opportunities, analyzes orderbook depth and imbalances, classifies market regimes (trending, ranging, volatile), and screens across all markets for trading opportunities. Use this skill when the user asks about technical analysis on Paradex, market conditions, support/resistance levels, indicators, funding rate screening, orderbook depth, "what's the market doing", "is BTC trending", "find me opportunities", "market overview", "top movers", or any analytical question about Paradex market data and conditions.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, progress reporting
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2640 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 727: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.