How do I install the Admin Devops skill?

Run npx skillmds@latest add evolv3ai/admin-devops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Admin Devops safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Admin Devops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Admin Devops free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Admin Devops?

evolv3ai (@evolv3ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Admin Devops by evolv3ai — Agent Skill

Name: Admin Devops
Rating: 4.2 (5 reviews)
Author: evolv3ai

Admin Devops

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.

evolv3ai Updated Sep 22, 2026

File contents

Admin DevOps - Remote Infrastructure (Alpha)

CRITICAL MUST: Secrets and .env

NEVER store live .env files or credentials inside any skill folder.
.env.template files belong only in templates/ within a skill.
Store live secrets in ~/.admin/.env (or another non-skill location you control) and reference them from there.

⚠️ PROFILE GATE (MANDATORY)

See references/profile-gate.md (synced from admin).

Task Qualification (MANDATORY)

If the task is local OS/MCP/skills, stop and hand off to admin.
If the task is remote infrastructure, continue.
If ambiguous, ask a clarifying question before proceeding.

Task Routing

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

Server Operations

Use profile.servers for inventory; do not maintain a separate list.

Provisioning Workflow (5 Steps)

Choose provider
Load deployment env (.env.local)
Run provider workflow
Update profile servers/deployments
Log the operation

Logging (MANDATORY)

Uses local logging scripts (synced from admin):

source ~/.claude/skills/admin-devops/scripts/log-admin-event.sh
log_admin_event "Provisioned Hetzner server" "OK"

. "$HOME\.claude\skills\admin-devops\scripts\Log-AdminEvent.ps1"
Log-AdminEvent -Message "Provisioned Hetzner server" -Level OK

Scripts / References

Provider scripts: scripts/oci-* and related tools
App scripts: scripts/coolify-*, scripts/kasm/*
References: references/*.md
Templates: templates/*

---name: admin-devopsdescription: 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.license: MIT---# Admin DevOps - Remote Infrastructure (Alpha)## CRITICAL MUST: Secrets and .env- NEVER store live `.env` files or credentials inside any skill folder.- `.env.template` files belong only in `templates/` within a skill.- Store live secrets in `~/.admin/.env` (or another non-skill location you control) and reference them from there.---## ⚠️ PROFILE GATE (MANDATORY)See `references/profile-gate.md` (synced from admin).## Task Qualification (MANDATORY)- If the task is **local OS/MCP/skills**, stop and hand off to **admin**.- If the task is **remote infrastructure**, continue.- If ambiguous, ask a clarifying question before proceeding.## Task Routing| 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** |## Server OperationsUse profile.servers for inventory; do not maintain a separate list.## Provisioning Workflow (5 Steps)1. Choose provider2. Load deployment env (`.env.local`)3. Run provider workflow4. Update profile servers/deployments5. Log the operation## Logging (MANDATORY)Uses local logging scripts (synced from admin):```bashsource ~/.claude/skills/admin-devops/scripts/log-admin-event.shlog_admin_event "Provisioned Hetzner server" "OK"``````powershell. "$HOME\.claude\skills\admin-devops\scripts\Log-AdminEvent.ps1"Log-AdminEvent -Message "Provisioned Hetzner server" -Level OK```## Scripts / References- Provider scripts: `scripts/oci-*` and related tools- App scripts: `scripts/coolify-*`, `scripts/kasm/*`- References: `references/*.md`- Templates: `templates/*`

Frequently asked questions