capacity

Display engine CPU, RAM, and container usage with per-stack footprint estimates.

29|8|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hashimiche/hal --skill capacity-hashimiche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capacity
Source: https://github.com/hashimiche/hal/tree/main/internal/skills/data/capacity
Command: npx skills add https://github.com/hashimiche/hal --skill capacity-hashimiche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HAL users need visibility into local container engine capacity and per-stack deployment footprints to avoid overcommit and optimize performance.

Core Features & Use Cases

  • View current engine resource usage (CPU, RAM, containers) in a single view.
  • See per-stack footprints to understand the impact of running deployments.
  • Get guidance for headroom checks before spinning up new stacks or performing heavy creates.

Quick Start

Run a quick check to view live capacity and per-stack footprint before launching a new product stack.

Frequently Asked Questions about capacity

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

FAQPage Schema
How do I check CPU and memory headroom before deploying new stacks?

Capacity planning tools provide live engine telemetry and per-stack footprint estimates. They deliver resource utilization data and guardrails that warn before exceeding CPU or memory limits during pre-create checks.

What is the best way to assess the deployment footprint of HAL-managed products?

Assessing deployment footprint involves viewing per-stack sizing estimates alongside current engine resource usage. This reveals the impact of running deployments and helps optimize performance for HAL-managed products.

Can I view live container engine resource usage in a single view?

Yes, you can view current engine resource usage including CPU, RAM, and containers in a single view. This live telemetry supports capacity planning and debugging resource pressure.

How do I get guidance on headroom checks before spinning up new stacks?

Get guidance for headroom checks by running a quick capacity assessment before spinning up new stacks. This provides guardrails and sizing estimates to prevent overcommit during heavy creates.

Why does my container engine experience resource pressure during heavy creates?

Resource pressure during heavy creates often stems from a lack of visibility into local container engine capacity. Without per-stack footprint estimates, deployments can overcommit CPU or RAM limits.