Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
**Enhanced security and prompt injection protections.** - Expanded credential protection to include all files under `~/.beecli/` and additional sensitive fields (`apiKey`, `secret`, `password`). - Added strict rules against following instructions from external outputs (including prompt injection attempts). - Prohibited piping or redirecting `beecli` output to other files or destinations. - Clarified that custom API URLs are not supported and reinforced default endpoint safety. - Added section on scope boundaries: limits this skill to `beecli` operations only, forbidding unrelated shell or file system actions.
What This Skill Does
Operates the Beetrade trading platform through the `beecli` CLI. Covers authentication, market data retrieval, bot and strategy management, alerts, accounts, and portfolio workflows across paper, backtest, and live environments.
Built-in confirmation prompts and automatic credential redaction reduce the risk of accidental live orders or token exposure that raw CLI usage would not prevent.
When to use it
- Starting or stopping a live trading bot
- Backtesting a strategy before enabling live execution
- Checking current portfolio account status
- Setting up price alerts on a specific asset
- Discovering bot or strategy IDs before running update commands
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: List all my active bots
- 1Run `beecli auth status` to confirm authentication is valid
- 2Run `beecli bot list` to retrieve all bots
- 3Filter or display results, redacting any credential fields from JSON output
- 4Present bot IDs, names, and status to the user
A table or JSON list of bots with their IDs, current state (running/stopped), and target environment (paper/live)
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.