# Beetrade

> Use Beecli to interact with the Beetrade platform for authentication, market data, bot/strategy operations, alerts, accounts, and portfolio workflows. Use this skill whenever a user asks to run or troubleshoot Beecli commands.

- Skill: `johnalbertini14-glitch/beetrade` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add johnalbertini14-glitch/beetrade`
- Raw SKILL.md: https://api.skillmd.com/api/skills/johnalbertini14-glitch/beetrade/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: johnalbertini14-glitch (https://skillmd.com/u/johnalbertini14-glitch)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/johnalbertini14-glitch/beetrade

---


# Beetrade Skill

Use this skill to operate `beecli` safely and efficiently.

## Quick Start

1. Confirm `beecli` exists: `beecli --help`.
2. Check auth state first: `beecli auth status`.
3. If unauthenticated, run `beecli auth login` to interactively continue the login flow.
4. Run read-only/list/get command first to discover IDs before write actions.
5. For mutating operations, restate exact command and impact before executing.

## Safety Rules

Always require explicit user confirmation immediately before executing these actions:

- Any live trading start/stop command.
- Any delete command.
- Any command that updates account credentials.
- Any command that can place real orders or alter scheduled execution.

Default to safer alternatives first:

- Prefer `paper` or `backtest` before `live`.
- Prefer `list/get/status/detail` before `update/delete/run`.

If command intent is ambiguous, ask one clarifying question before running anything.

## Execution Workflow

When a user asks for an operation, follow this sequence:

1. **Understand intent**: identify resource type (bot, strategy, alert, account, etc.) and target environment (paper/live).
2. **Validate prerequisites**:
- Auth is valid (`beecli auth status`).
- Required IDs are available; if not, discover via list commands.
- Required JSON payload exists and is valid JSON.
3. **Preview**: show the exact command you plan to execute.
4. **Confirm if risky**: apply safety rules above.
5. **Execute and report**:
- Return parsed JSON result if successful.
- On failure, include command attempted, error summary, and likely fix.

## JSON Input Guidance

Commands using `-c` or `-d` require JSON strings. If the user gives partial fields:

1. Draft a minimal valid JSON payload.
2. Ask for missing required fields.
3. Use single quotes around the JSON string in shell examples.

## Where To Look For Command Syntax

Use [references/commands.md](references/commands.md) for the full command catalog and examples.

## Notes

- Config file location: `~/.beecli/config.json`
- Default API URL: `https://api.prod.beetrade.com/api/v2`
- Command actions generally emit JSON; CLI help/argument validation output may not be JSON.