AB paradex-strategy-builder
Design, backtest, and reason about trading strategies for Paradex using MCP tools. Takes natural language strategy descriptions and turns them into structured trading plans with entry/exit rules, position sizing, risk parameters, and historical validation using Paradex kline and trade data. Supports strategy templates for common approaches (funding arb, mean reversion, momentum, grid trading, basis trading). Use this skill whenever the user asks to build a trading strategy for Paradex, wants to backtest an idea, asks about "how would X strategy work on Paradex", wants to design entry/exit rules, asks about grid trading, funding arbitrage, mean reversion, momentum strategies, or any systematic trading approach on Paradex markets. Also trigger for "build me a bot", "trading plan", "strategy for BTC-USD-PERP", "backtest this idea", or "how would I trade [pattern] on Paradex".
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 70Failures and branches. 4 branches
- 100Steps. 75 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2231 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)
- +3Description length 885: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 17 headings
- +3Step-by-step instructions: 75 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.