abx-resource-capacity

Sizes AgentBox warm pools, configures autoscaling groups, and diagnoses stuck sandbox capacity.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sandbox workloads stall when warm pools are undersized, autoscaling bounds are misconfigured, or quota ceilings block growth, leaving sandboxes queued or failing to start. This Skill guides you through sizing pools, tuning autoscaling groups, reading quota, and recovering pools that refuse to grow. ## Core Features & Use Cases - Pool Sizing: Set replicas directly on fixed pools or edit autoscaling group bounds when the autoscaler owns the size, using abx scale and abx update commands. - Stuck Pool Recovery: Diagnose why a pool will not grow by checking pool status, quota, and cluster events, then apply the counter-intuitive fix of reducing the replica target before climbing again. - Capacity Planning: Plan for N concurrent sandboxes by inspecting instance types, committed quota, and peak concurrency rather than total work. - Use Case: A reinforcement learning rollout needs 50 concurrent sandboxes but they keep queuing. Use this Skill to check the pool's desired versus actual replicas, confirm quota headroom, and set the group's maxReplicas to the true peak. ## Quick Start Ask the AI to check why the demo-1c2gi pool in the demo environment is stuck below its target size and fix the capacity.

Frequently Asked Questions about abx-resource-capacity

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

FAQPage Schema
How do I resize a sandbox warm pool with the abx CLI?

Resize a pool with `abx scale envs <env> pools <pool> --replicas N` when its autoscaling group is off. If autoscaling is on, the autoscaler owns replicas, so edit the group's bounds with `abx update envs <env> scaling-groups <group> -f group.json` instead.

Why is my sandbox pool stuck below its target replicas?

A pool stays stuck when it requests more Pods than the cluster can place or when team quota blocks growth. Check pool status, `abx quotas`, and `abx envs <env> events`, then reduce the replica target so the reservation succeeds and climb from there.

How does demand-anchored autoscaling work for sandbox pools?

The autoscaler scales toward actual demand, meaning running sandboxes plus queued requests, plus a buffer, capped by a per-mode ceiling. Conservative, Default, and Aggressive modes control the scale-up buffer and scale-down step size.

Does setting a high maxReplicas make the pool scale to that size?

No, a wide maxReplicas is only a ceiling, not a target. Scale-up is anchored on real demand, so setting 0-2560 does not request 2560 Pods; it only permits growth up to that bound when demand exists.

How many replicas do I need for N concurrent sandboxes?

Size the pool for peak concurrency, not total work. A rollout running 1000 episodes 50 at a time needs 50 claimable Pods; check `abx instancetypes` and `abx quotas` first, then set the group's maxReplicas at that peak.