Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From opentradex-trade
Open a paper long position on any enabled rail — Kalshi, Polymarket, Alpaca, or Coinbase. Invoke when the user says "buy", "go long", "paper long", "yes on <market>", or confirms a suggested entry. Requires rail, symbol, qty; price is optional (defaults to a mid-market mark).
How this skill is triggered — by the user, by Claude, or both
Slash command
/opentradex-trade:buyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Open a long paper position.
Open a long paper position.
User arguments: $ARGUMENTS — expected form <rail> <symbol> <qty> [price].
rail, symbol, qty, optional price). If anything is missing, ask for exactly what's missing in one short sentence — don't re-ask fields the user already gave.node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" risk
If openPositions ≥ 5 or dailyTotal ≤ -50, warn the user and confirm before proceeding.node "${CLAUDE_PLUGIN_ROOT}/bin/tradex.js" buy $ARGUMENTS/opentradex-trade:sell <position-id>."/opentradex-trade:onboard first.npx claudepluginhub deonmenezes/opentradex-harness --plugin opentradex-tradeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.