Skip to content

AI Agents

Use Bullpen CLI with Claude Code, Codex CLI, Gemini CLI, or OpenClaw to research markets, inspect your account, and run documented Bullpen workflows from natural language.

Setup

Install and authenticate the CLI first, then install the agent skills:

bullpen login
bullpen status
bullpen skill install

Restart your AI assistant after bullpen skill install. Agents load skills at startup, so an already-running Claude Code, Codex, Gemini, or OpenClaw session will not see newly installed or updated Bullpen instructions until it restarts.

To target one assistant explicitly:

bullpen skill install --claude
bullpen skill install --codex
bullpen skill install --gemini
bullpen skill install --openclaw

Use --dry-run or --check when you want to inspect or validate the target without changing files. Use --read-only when you want the installed skill to block mutating Bullpen commands.

What Agents Can Do

After the skill is installed and the assistant restarts, you can ask it to:

  • Discover and compare Prediction markets.
  • Check balances, positions, open orders, rewards, and points.
  • Preview or execute Polymarket-backed Prediction trades with bullpen trade.
  • Run bullpen fix --refresh when trading fails and bullpen support when support needs a redacted artifact.
  • Recover stuck Polymarket funds or resolved positions with bullpen recover.
  • Manage Perps (Hyperliquid) account, order, and position workflows exposed by the CLI.
  • Use experimental Onchain (Solana) token reads, swaps, limit orders, DCA, and portfolio commands.
  • Fill March Madness brackets and use Bullpen bracket workflows.
  • Diagnose common setup and account issues without asking users to manually choose advanced wallet or exchange diagnostics first.

Money-moving commands still use the CLI's normal safety model: previews are available where supported, live execution requires the relevant command flags, and account state comes from your authenticated Bullpen session.

For Prediction market workflows, instruct agents to start with:

bullpen fix --refresh
bullpen polymarket search "bitcoin" --type market --limit 5
bullpen trade buy will-ronaldo-cry-at-the-world-cup-20260604013616610 No 5 --preview --output json
bullpen recover polymarket
bullpen support

Advanced Polymarket wallet, CLOB, and relayer commands remain available in the reference, but they should be escalation commands. Use them only when the simplified command output or Bullpen support asks for that exact evidence.

Installed Skill Locations

bullpen skill install writes the bullpen-cli skill into detected assistant config directories. Personal installs use these paths:

Assistant Default skill path
Claude Code ~/.claude/skills/bullpen-cli/
Codex CLI ~/.codex/skills/bullpen-cli/
Gemini CLI ~/.gemini/skills/bullpen-cli/
OpenClaw ~/.openclaw/skills/bullpen-cli/
Cross-tool standard ~/.agents/skills/bullpen-cli/

When a non-Claude assistant is detected, Bullpen also writes the cross-tool standard copy under ~/.agents/skills/bullpen-cli/. Project installs use .claude/skills/bullpen-cli/ for Claude Code and .agents/skills/bullpen-cli/ for the other assistants.

Public Skill Manifest

The public mirror lives at docs/public/skill/SKILL.md, with supporting references under docs/public/skill/references/. It is generated from the maintained skill source and embedded into the CLI binary for bullpen skill install. Treat it as a published manifest, not a hand-edited user config file.

Seeing version: "0.0.0" in the public mirror is expected. Source-controlled skill manifests keep 0.0.0 as an install-time placeholder. During bullpen skill install and bullpen skill update, the CLI stamps installed copies with the running Bullpen CLI version so bullpen skill list can detect outdated local skills.

References