abx-common

Configures abx CLI authentication, cluster selection, output formats, and approval-gated writes for the AgentBox platform.

11|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/scitix/Agent-Sandbox --skill abx-common-scitix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abx-common
Source: https://github.com/scitix/Agent-Sandbox/tree/main/plugin/skills/abx-common
Command: npx skills add https://github.com/scitix/Agent-Sandbox --skill abx-common-scitix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Connecting an agent to an AgentBox platform fails in predictable ways: wrong endpoint, wrong cluster, unreadable output, or writes that silently wait for human approval. This Skill provides the shared operational knowledge every other abx skill relies on for those four concerns. ## Core Features & Use Cases - Authentication setup: Resolve the console endpoint and API key via flags, environment variables, or config file, and verify identity with abx whoami. - Cluster targeting: Choose the correct cluster per command with --cluster, including the single-cluster auto-fill and the --cluster-api exception case. - Machine-readable output: Switch between table, --json, and --csv output, filter lists by column heading, and pipe results into jq or shell loops. - Safe writes with approval flow: Generate write payloads from --schema or --editable instead of memory, and interpret APPROVAL_REQUIRED versus FORBIDDEN_FOR_AGENT responses correctly. - Use Case: An agent's abx envs call fails with an authentication error. Use this Skill to diagnose whether the endpoint, key, or cluster selection is at fault, then re-run with the correct configuration. ## Quick Start Ask the agent to run abx agent-context and then list the environments on a specific cluster using JSON output.

Frequently Asked Questions about abx-common

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate the abx CLI with an AgentBox platform?

Set the console address with --endpoint or AGENTBOX_ENDPOINT and the credential with --api-key or AGENTBOX_API_KEY. Values resolve as flag, then environment, then ~/.config/abx/config.json. Run abx whoami to confirm which identity the key acts as.

How do I choose a cluster for an abx command?

Pass --cluster <cluster-id> or set AGENTBOX_CLUSTER per command; the cluster is never part of the context. Run abx clusters to list what the deployment reaches, and when exactly one cluster exists it is filled in automatically.

Why does my abx write command return APPROVAL_REQUIRED?

Writes made with an agent key are held for a person to release, and the command returns a link for that approval. Re-run the same command after the person acts; it is not an error to work around.

What is the difference between APPROVAL_REQUIRED and FORBIDDEN_FOR_AGENT in abx?

APPROVAL_REQUIRED means a person is about to decide, so re-run the command shortly. FORBIDDEN_FOR_AGENT means no approval exists or ever will, as with issuing or promoting API keys, so stop and hand the console link to a person.

How do I get machine-readable output from abx commands?

Add --json for the raw API shape or --csv for flat output, and use --filter key=value with a column heading to narrow lists. The default table output includes hints and console links but is truncated at 200 rows.

Should I use abx or the E2B SDK to create a sandbox?

Use the E2B SDK for creating sandboxes, running commands, and reading filesystems; abx manages the platform side such as environments, pools, and scaling. Run abx envs <env> docs to get the E2B-compatible endpoints for your cluster before creating a sandbox.