How do I install the Beetrade skill?

Run npx skillmds@latest add johnalbertini14-glitch/beetrade in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Beetrade safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Beetrade?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Beetrade free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Beetrade?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Beetrade by johnalbertini14-glitch — Agent Skill

Name: Beetrade
Rating: 4.666666666666667 (3 reviews)
Author: johnalbertini14-glitch

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.

File contents

Beetrade Skill

Use this skill to operate beecli safely and efficiently.

Quick Start

Confirm beecli exists: beecli --help.
Check auth state first: beecli auth status.
If unauthenticated, run beecli auth login to interactively continue the login flow.
Run read-only/list/get command first to discover IDs before write actions.
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:

Understand intent: identify resource type (bot, strategy, alert, account, etc.) and target environment (paper/live).
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.

Preview: show the exact command you plan to execute.
Confirm if risky: apply safety rules above.
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:

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

Where To Look For Command Syntax

Use 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.

---name: beetradedescription: 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.---# Beetrade SkillUse this skill to operate `beecli` safely and efficiently.## Quick Start1. 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 RulesAlways 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 WorkflowWhen 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 GuidanceCommands 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 SyntaxUse [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.

Frequently asked questions