REMOTE infrastructure administration (alpha v0.0.2). Server inventory, cloud provisioning (OCI, Hetzner, Linode, DigitalOcean, Contabo), and application deployment (Coolify, KASM). Profile-aware - reads servers from device profile. Use when: provisioning VPS, deploying to cloud, installing Coolify/KASM, managing remote servers. NOT for: local installs, Windows/WSL/macOS admin, MCP servers → use admin.
.env files or credentials inside any skill folder..env.template files belong only in assets/ within a skill.~/.admin/.env (or another non-skill location you control) and reference them from there.See references/profile-gate.md (synced from admin).
| Task | Reference |
|---|---|
| Server inventory | Server Operations |
| OCI provisioning | references/oci.md |
| Hetzner provisioning | references/hetzner.md |
| Linode provisioning | references/linode.md |
| DigitalOcean provisioning | references/digitalocean.md |
| Contabo provisioning | references/contabo.md |
| Coolify deployment | references/coolify.md |
| KASM deployment | references/kasm.md |
| Local machine tasks | → Use admin skill |
Use profile.servers for inventory; do not maintain a separate list.
.env.local)Logging scripts live in the admin skill. From commands or agents (where
${CLAUDE_PLUGIN_ROOT} is available), source them as:
source "${CLAUDE_PLUGIN_ROOT}/skills/admin/scripts/log-admin-event.sh"
log_admin_event "Provisioned Hetzner server" "OK"
. "${CLAUDE_PLUGIN_ROOT}\skills\admin\scripts\Log-AdminEvent.ps1"
Log-AdminEvent -Message "Provisioned Hetzner server" -Level OK
When running from a SKILL.md context, resolve the admin skill path from the
plugin directory structure (sibling skill under skills/admin/).
Script path resolution: When Claude Code loads this file, it provides the full
path. All scripts/ references below are relative to this file's directory.
scripts/agentDevopsInventory.ts, scripts/agent_devops_inventory.pyreferences/*.md (per-provider deployment guides)