Agent skill
vps-docker
Full VPS Docker status — all containers, resource usage, arifOS health
Install this agent skill to your Project
npx add-skill https://github.com/ariffazil/arifOS/tree/main/skills/vps-docker
SKILL.md
VPS Docker Manager
When the user asks about containers, docker status, VPS health, or what's running:
- Run
ssh arifos "docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}'"to list all containers - Run
ssh arifos "docker stats --no-stream --format 'table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}'"for resource usage - Run
ssh arifos "curl -s http://localhost:8080/health | jq '{status,tools_loaded,version}'"for arifOS health - Show disk:
ssh arifos "df -h /"
Present as a clean status table. Flag any containers not in healthy or Up state.
Trigger patterns: "docker status", "containers", "what's running", "vps status", "system health", "container status"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
mcp-config-separation
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
MCP_CONFIG
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow — human applies via git.
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow — human applies via git.
Didn't find tool you were looking for?