blaxel-ai/agent-skills

blaxel-cli

Manage Blaxel resources from the command line using the bl CLI. Deploy agents, sandboxes, jobs, and MCP servers. Also installs the Blaxel CLI if not present.

First seen Apr 2, 2026

Installation

$ npx skills add blaxel-ai/agent-skills --skill blaxel-cli

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from blaxel-ai/agent-skills.

npx skills add blaxel-ai/agent-skills

Browse all from blaxel-ai/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(bl:*), Bash(curl:*)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 7,667 B
  • docs SUMMARY.md 172 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 409 installs

SKILL.md

Blaxel CLI

A CLI to manage Blaxel cloud resources from the command line: agents, sandboxes, jobs, MCP servers, drives, and more.

Prerequisites

The bl command must be available on PATH. To check:

bl version

If not installed, install via the official install script:

curl -fsSL https://raw.githubusercontent.com/blaxel-ai/toolkit/main/install.sh | sh

Or via Homebrew:

brew tap blaxel-ai/blaxel && brew install blaxel

After installation, log in to your workspace:

bl login my-workspace

Global Flags

All commands support these flags:

Flag Description
-o, --output <format> Output format: pretty, yaml, json, table
-w, --workspace <name> Override workspace for this command
-v, --verbose Enable verbose output
-u, --utc Enable UTC timezone
--skip-version-warning Skip version warning

Non-Interactive Mode

For commands that prompt for input (confirmations, selections), add -y or --yes to auto-confirm. This is required when running in non-interactive / no-TTY environments (scripts, CI, agents).

Available Commands

bl apply       # Apply configuration changes to resources declaratively using YAML files.
bl chat        # Start an interactive chat session with a deployed agent.
bl connect     # Open an interactive terminal session to a sandbox
bl delete      # Delete Blaxel resources from your workspace.
bl deploy      # Deploy your Blaxel project to the cloud.
bl drive       # Manage drives and drive mounts on sandboxes.
bl fork        # Create a new sandbox or application by forking an existing sandbox.
bl get         # Retrieve information about Blaxel resources in your workspace.
bl login       # Authenticate with Blaxel to access your workspace.
bl logout      # Remove stored credentials for a workspace.
bl logs        # View logs for Blaxel resources.
bl new         # Create a new Blaxel resource from templates.
bl push        # Build and push a container image to the Blaxel registry without creating a deployment.
bl run         # Execute a Blaxel resource with custom input data.
bl serve       # Start a local development server for your Blaxel project.
bl share       # Share Blaxel resources with other workspaces in your account.
bl token       # Retrieve the authentication token for the specified workspace.
bl unshare     # Remove shared Blaxel resources from other workspaces.
bl upgrade     # Upgrade the Blaxel CLI to the latest version.
bl version     # Print the version number
bl workspaces  # List and manage Blaxel workspaces.

Reference Documentation

  • [apply](references/apply.md) - Apply configuration changes to resources

declaratively using YAML files.

  • [chat](references/chat.md) - Start an interactive chat session with a deployed

agent.

  • [connect](references/connect.md) - Open an interactive terminal session to a

sandbox

  • [delete](references/delete.md) - Delete Blaxel resources from your workspace.
  • [deploy](references/deploy.md) - Deploy your Blaxel project to the cloud.
  • [drive](references/drive.md) - Manage drives and drive mounts on sandboxes.
  • [fork](references/fork.md) - Create a new sandbox or application by forking an

existing sandbox.

  • [get](references/get.md) - Retrieve information about Blaxel resources in your

workspace.

  • [login](references/login.md) - Authenticate with Blaxel to access your

workspace.

  • [logout](references/logout.md) - Remove stored credentials for a workspace.
  • [logs](references/logs.md) - View logs for Blaxel resources.
  • [new](references/new.md) - Create a new Blaxel resource from templates.
  • [push](references/push.md) - Build and push a container image to the Blaxel

registry without creating a deployment.

  • [run](references/run.md) - Execute a Blaxel resource with custom input data.
  • [serve](references/serve.md) - Start a local development server for your

Blaxel project.

  • [share](references/share.md) - Share Blaxel resources with other workspaces in

your account.

  • [token](references/token.md) - Retrieve the authentication token for the

specified workspace.

  • [unshare](references/unshare.md) - Remove shared Blaxel resources from other

workspaces.

  • [upgrade](references/upgrade.md) - Upgrade the Blaxel CLI to the latest

version.

  • [version](references/version.md) - Print the version number
  • [workspaces](references/workspaces.md) - List and manage Blaxel workspaces.

Discovering Options

To see available subcommands and flags, run --help on any command:

bl --help
bl deploy --help
bl get --help
bl get agents --help

Common Workflows

Create a sandbox, run a command, and get its logs

# 1. Create a sandbox with bl apply
bl apply -f - <<EOF
apiVersion: blaxel.ai/v1alpha1
kind: Sandbox
metadata:
  name: my-sandbox
spec:
  runtime:
    image: blaxel/base-image:latest
    memory: 2048
  lifecycle:
    expirationPolicies:
      - type: ttl-idle
        value: 1h       # Delete after 1 hour of inactivity. Units: h, d, w
        action: delete
EOF

# 2. Retrieve sandbox configuration
bl get sandbox my-sandbox

# 3. Execute a command in the sandbox and get stdout of the command
bl run sandbox my-sandbox --path /process --data '{"command": "echo hello world", "name": "my-cmd", "waitForCompletion": true}'

# 4. Retrieve the logs for that command in case stdout was not sufficient
bl logs sandbox my-sandbox my-cmd

Run a complex command in a sandbox (agent guideline)

bl run sandbox ... --path /process --data '<json>' requires the JSON payload to survive shell quoting. As soon as the command embeds nested quotes, backslashes, multiple lines, or interpreters like sh -lc / python3 -c, inline --data becomes brittle and the API rejects the request with 400 Bad Request: invalid character ... in string escape code.

Decision rule for an agent:

  1. Command has no single quotes, no backslashes, no newlines → use

--data '{"command": "...", "waitForCompletion": true}' directly.

  1. Anything more complex (nested quotes, escapes, multiline, scripts) → **write

the JSON payload to a file** with your Write/file-creation tool (this bypasses the shell entirely), then run with --file.

# Step 1 — agent writes /tmp/process.json with content like:
# {
#   "command": "sh -lc 'python3 -c \"print(\\\"hello\\\")\"'",
#   "name": "cve-check",
#   "waitForCompletion": true
# }
#
# Step 2 — execute it
bl run sandbox my-sandbox --path /process --file /tmp/process.json

Deploy an agent

bl new agent my-agent
cd my-agent
bl serve --hotreload    # Test locally
bl deploy               # Deploy to cloud
bl chat my-agent        # Chat with it

Manage sandboxes

bl get sandboxes                    # List all
bl get sandbox my-sandbox --watch   # Watch status
bl connect sandbox my-sandbox       # Interactive terminal
bl logs sandbox my-sandbox --follow # Stream logs
bl delete sandbox my-sandbox        # Clean up

Multi-workspace deployment

bl workspaces dev     # Switch to dev
bl deploy             # Deploy to dev
bl workspaces prod    # Switch to prod
bl deploy             # Deploy to prod