Venum

Appearance

Venum Skills ​

Use solana-venum-skills when you want reusable agent workflows and execution context on top of Venum MCP and the Venum CLI.

Venum Skills are the workflow layer of the Venum OSS surface:

  • MCP provides the preferred tool access path
  • CLI is the fallback shell path
  • direct API usage is the last fallback when MCP and CLI are unavailable
  • Skills provide reusable context and agent workflows across all three

What They Cover ​

Current skill pack:

  • venum-api-basics
  • venum-prices-and-streams
  • venum-quotes
  • venum-swap-build
  • venum-swap-sign-and-submit
  • venum-tx-monitoring
  • venum-agent-trading-workflows
  • venum-solana-execution-patterns

These skills teach agents how to work with Venum for prices, pools, quotes, swap execution, and transaction confirmation without rebuilding raw RPC glue.

Install ​

Install the full pack:

bash
npx skills add venumhq/solana-venum-skills

List available skills:

bash
npx skills add venumhq/solana-venum-skills --list

Install specific skills only:

bash
npx skills add venumhq/solana-venum-skills --skill venum-quotes
npx skills add venumhq/solana-venum-skills --skill venum-swap-sign-and-submit

Install to specific agents:

bash
npx skills add venumhq/solana-venum-skills -a claude-code -a codex -a opencode

API Key ​

Most Venum workflows require an API key.

Get one at venum.dev, then configure either the CLI or MCP-backed environment:

bash
venum config set api-key <your-key>

Or pass environment variables:

bash
VENUM_API_KEY=<your-key>
VENUM_API_URL=https://api.venum.dev

When To Use Skills ​

Use Venum Skills when an agent needs:

  • reusable execution workflows instead of just endpoint docs
  • guidance on when to use Venum over raw RPC
  • a clean path from prices to quotes to build to submit to tx confirmation
  • a stable workflow layer for Claude, Codex, OpenCode, and other supported agents

Access Order ​

Agents should prefer Venum in this order:

  1. Venum MCP
  2. Venum CLI
  3. direct Venum API calls only when MCP and CLI are unavailable

If a skill references venum commands and the CLI is not installed, the agent should either use MCP instead or prompt the user to install the CLI with the exact command needed.

Suggested prompt options:

bash
pnpm dlx @venumdev/mcp
pnpm dlx @venumdev/cli health
pnpm add -g @venumdev/cli