From opentradex-trade
One-time interactive setup that stores API keys for Kalshi, Polymarket, Alpaca, and Coinbase so OpenTradex can scan markets and paper-trade. Invoke this the very first time a user says "set up OpenTradex", "add my keys", or "start trading". Safe to re-run to add or update a rail.
How this skill is triggered — by the user, by Claude, or both
Slash command
/opentradex-trade:onboardThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are onboarding a new user to the OpenTradex paper-trading plugin.
You are onboarding a new user to the OpenTradex paper-trading plugin.
Collect API keys only. v1 of this plugin is paper-only — the keys are used for authenticated read-scans (higher rate limits, better data) and are persisted locally at ~/.claude/opentradex/keys.json with 0600 permissions. No live orders are placed.
"I'll ask for your API keys for each exchange. Leave any rail blank to skip it — you can add it later. Keys never leave your machine."
node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" onboard
This will prompt for each rail in turn: Kalshi, Polymarket, Alpaca (key + secret), Coinbase (key + secret).node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" status
node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" keys
~/.claude/opentradex/keys.json.node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" keys-delete <rail>./opentradex-trade:scan to see live markets."npx claudepluginhub deonmenezes/opentradex-harness --plugin opentradex-tradeCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.