dradis-tactical-command

Monitor and configure the DRADIS prediction-market trading engine via its REST API.

27|11|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mbordash/DRADIS --skill dradis-tactical-command-mbordash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dradis-tactical-command
Source: https://github.com/mbordash/DRADIS/tree/main/integrations/openclaw
Command: npx skills add https://github.com/mbordash/DRADIS --skill dradis-tactical-command-mbordash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating a live prediction-market trading engine requires constant visibility into positions, P&L, strategy health, and configuration, and making safe config changes without risking real capital through mistakes. ## Core Features & Use Cases - Live Monitoring: Query engine health, open and pending positions, portfolio value, session P&L, recent trades, telemetry, logs, and venue latency across Polymarket International, Polymarket US, and Kalshi builds. - Squadron & Strategy Diagnostics: List squadrons, inspect per-squadron configs, and use viper status to answer "why isn't DRADIS trading?" with named veto reasons. - Guard-railed Configuration: Validate fields against the config schema, then PATCH squadron or global config only after explicit human confirmation, with mandatory read-back verification since unknown keys are silently ignored. - LLM Advisor Oversight: Review LLM recommendations and approve or reject proposed AI config actions from the audit queue. - Use Case: Ask "Show me open positions and session P&L for BTC, then confirm before raising the adverse block threshold on btc-hourly" and the agent reads the current value, validates bounds, and applies the change only after your approval. ## Quick Start Ask the agent to show the current status of DRADIS, including open positions, squadron list, and session P&L.

Frequently Asked Questions about dradis-tactical-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check why my DRADIS trading bot is not trading?

Call the get_viper_status tool, which reports each strategy's last evaluation time, outcome, and the named gate that vetoed the last entry attempt. Recent evaluations with named reasons mean the engine is healthy and correctly sitting out; idle means no tradeable market is available.

How do I change a DRADIS strategy parameter safely?

Use patch_squadron_config with a flat JSON body after validating the field with get_config_schema and getting explicit user confirmation. Always read the changed field back from the response, because unknown keys are silently ignored while still returning 200 OK.

Does the DRADIS skill support Kalshi and Polymarket US?

Yes, the skill works with all three venue builds: Polymarket International, Polymarket US, and Kalshi. Call get_deployment_region to identify the active build, since some endpoints like on-chain wallet probes are only available on the international build.

Can this skill close positions or deploy new squadrons?

No. The skill is monitoring and configuration only by design and deliberately omits position exit, position sync, and squadron deployment endpoints. Perform those capital-committing actions in the DRADIS Control Tower UI.

Why do I get 401 or 403 errors from the DRADIS API?

A 401 means the X-API-Key header is missing or wrong, so configure DRADIS_API_KEY to match the engine's environment variable. A 403 means the engine runs with DRADIS_READ_ONLY=true, which rejects every non-GET request at the engine level.