box-ops

Governs safe SSH operations, container management, and port allocation across shared production hosts.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/Harbour-Emerge/skills --skill box-ops-harbour-emerge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: box-ops
Source: https://github.com/Harbour-Emerge/skills/tree/main/box-ops
Command: npx skills add https://github.com/Harbour-Emerge/skills --skill box-ops-harbour-emerge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating on shared production servers risks accidentally destroying other tenants' containers, claiming occupied ports, or acting on misleading system readings. This Skill encodes the host map, tenant boundaries, port ownership, and hard safety rules so every remote command is informed before it runs. ## Core Features & Use Cases - Host and Tenant Map: Documents SSH access for the shared demo VM and editone-prod, the four-tenant container layout, and which containers are safe to touch. - Port and Resource Facts: Lists public and loopback port ownership, the real Docker disk location, RAM limits, and Cloud SQL connection details to prevent false conclusions from misleading readings like df /. - Safety Guardrails: Defines a read-before-write triage sequence, forbidden commands (docker system prune, volume removal, destructive migrations), and an escalation pattern for actions requiring a human. - Use Case: Before debugging a failing container on the demo box, load this Skill to confirm the container belongs to your tenant, check the correct disk and memory metrics, and follow the safe triage sequence instead of restarting shared services. ## Quick Start Before running any command on a remote host, ask the AI to load the box-ops skill and confirm which containers and ports are safe to touch for this task.

Frequently Asked Questions about box-ops

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

FAQPage Schema
How do I safely debug a container on a shared production server?

Start with read-only commands: docker ps to list containers, docker logs on your own tenant's containers, free -h for memory, and df -h on the Docker data root. Never restart, prune, or reconfigure containers belonging to other tenants.

How do I check which ports are available before deploying a service?

Run sudo ss -tlnp to list bound ports, then compare against the documented port allocation table. Port 80 belongs to another tenant's nginx and cannot be claimed, while loopback ports like 8067-8069 are reserved for specific services.

Why does df show low disk space when Docker has plenty of room?

The root filesystem shows only ~3 GB free, but Docker's data root lives on a separate 99 GB disk at /opt/lms/docker with ~51 GB free. Always check df -h /opt/lms/docker and docker system df instead of trusting df /.

Can I run docker compose down on a shared multi-tenant host?

Only with an explicit -f flag pointing at your stack's compose file, since every stack pins its project name to prevent cross-tenant damage. Prefer docker compose stop over down, and never run down from a random directory.

What commands should never run on a shared Docker host?

Never run docker system prune in any form, docker volume rm, daemon restarts, destructive database migrations, or firewall changes. Volumes like caddy_data hold ACME certificates whose deletion burns Let's Encrypt rate limits.