devops

Name: devops
Author: evolv3-ai

github.com/evolv3-aiCloud & DevOps140 installsUpdated 14w ago

About devops

devops is a skill for operating remote infrastructure, with provider-specific skills handling provisioning and deployment tasks. It requires an admin profile, uses shared admin scripts for secrets and logging, and routes local machine work elsewhere.

Key features

01Mandatory admin profile check
02Server inventory from profile
03Secret retrieval with fallback
04Required operation logging
05Routing to provider skills

Use cases

01Checking remote server inventory
02Coordinating provider-specific provisioning
03Retrieving infrastructure API credentials
04Logging infrastructure operations

MCP support

Tasks involving local OS, MCP, or skills are routed to the admin skill; remote infrastructure tasks are handled here.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/evolv3-ai/vibe-skills --skill devops

After installing, type/devopsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/

agent-devops.env.template

devops-registry.json

env-spec.txt

env-template

provider-infrastructure-template

references/

DEPLOYMENT_WORKFLOWS.md

EXAMPLE_INVENTORY.md

INVENTORY_FORMAT.md

profile-gate.md

PROVIDER_DISCOVERY.md

TROUBLESHOOTING.md

Details

From the project README

Admin DevOps - Remote Infrastructure (Alpha)

Script path resolution: When Claude Code loads this file, it provides the full path. Derive SKILL_DIR from this file's directory. Admin scripts (profile gate, logging, secrets) live in the sibling admin skill at ${SKILL_DIR}/../admin/scripts/.

CRITICAL: Secrets and .env

NEVER store live .env files or credentials inside any skill folder.
.env.template files belong only in assets/ within a skill.
Store live secrets in ~/.admin/.env and reference from there.

Secrets Management

Three backends available, configured via ADMIN_SECRETS_BACKEND in ~/.admin/.env:

Backend	Storage	Best For
`infisical`	Infisical Cloud	Multi-device, audit trail
`vault` (default)	`$ADMIN_ROOT/vault.age`	Single device, offline
`env`	`$ADMIN_ROOT/.env`	Legacy

Fallback chain: infisical → vault → env. If the primary backend is unavailable, scripts automatically try the next.

CLI: Use the admin skill's secrets script to retrieve provider API keys:

# Retrieve a single provider token
HCLOUD_TOKEN=$(${SKILL_DIR}/../admin/scripts/secrets HCLOUD_TOKEN)

# Or if secrets is on PATH
export HCLOUD_TOKEN=$(secrets HCLOUD_TOKEN)

Provider Secrets Map

Secret Key	Infisical URI	Provider	Used By
`HCLOUD_TOKEN`	`infisical://admin-operator/prod/providers/hetzner/HCLOUD_TOKEN`	Hetzner	hcloud CLI auth
`DIGITALOCEAN_ACCESS_TOKEN`	`infisical://admin-operator/prod/providers/digitalocean/ACCESS_TOKEN`	DigitalOcean	doctl auth
`CNTB_OAUTH2_CLIENT_SECRET`	`infisical://admin-operator/prod/providers/contabo/CLIENT_SECRET`	Contabo	cntb config
`CNTB_OAUTH2_PASS`	`infisical://admin-operator/prod/providers/contabo/OAUTH_PASS`	Contabo	cntb config
`LINODE_API_TOKEN`	`infisical://admin-operator/prod/providers/linode/API_TOKEN`	Linode	linode-cli
`VULTR_API_KEY`	`infisical://admin-operator/prod/providers/vultr/API_KEY`	Vultr	vultr-cli
`CF_API_TOKEN`	`infisical://admin-operator/prod/network/cloudflare/API_TOKEN`	Cloudflare	Tunnel setup

Retrieval (v4.0+):

# URI-based (recommended)
HCLOUD_TOKEN=$(resolve-secret-ref.sh "infisical://admin-operator/prod/providers/hetzner/HCLOUD_TOKEN")

# Multi-project secrets CLI
HCLOUD_TOKEN=$(secrets --project admin-operator --path /providers/hetzner HCLOUD_TOKEN)

# Legacy (still works via fallback chain)
HCLOUD_TOKEN=$(secrets HCLOUD_TOKEN)

Guides: references/secrets-architecture.md (full 4-layer model), references/infisical.md (Infisical setup), references/vault-guide.md (age vault fallback)

Profile Gate (MANDATORY First Step)

Check for a profile before any operation. No profile means no server inventory, no preferences, no logging path.

${SKILL_DIR}/../admin/scripts/test-admin-profile.sh

Returns JSON: {"exists":true|false,"path":"...","device":"...","platform":"..."}

If exists: false — stop and hand off to admin skill for /setup-profile. Do not proceed without a profile.

Full details: references/profile-gate.md

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 (use profile.servers)
OCI provisioning	→ Use oci skill
Hetzner provisioning	→ Use hetzner skill
Linode provisioning	→ Use linode skill
DigitalOcean provisioning	→ Use digital-ocean skill
Contabo provisioning	→ Use contabo skill
Coolify deployment	→ Use coolify skill
KASM deployment	→ Use kasm skill
Secrets / Infisical setup	→ Use admin skill
Local machine tasks	→ Use admin skill

Server Operations

Use profile.servers[] for inventory; do not maintain a separate list. Profile is the source of truth.

Provisioning Workflow (5 Steps)

Choose provider
Load secrets via secrets CLI (provider API key)
Run provider workflow (use the dedicated provider skill)
Update profile.servers[] and profile.deployments{}
Log the operation via log_admin_event

Logging (MANDATORY)

Log every operation. Logging scripts live in the admin sibling skill.

source "${SKILL_DIR}/../admin/scripts/log-admin-event.sh"
log_admin_event "Provisioned Hetzner server hzn-01-203-42" "OK"
log_admin_event "OCI provisioning failed: OUT_OF_HOST_CAPACITY" "ERROR"

Levels: OK (success), INFO, WARN, ERROR

Architecture

Relationship to Admin

devops is a satellite of admin. It depends on admin for:

Profile gate (test-admin-profile.sh) — mandatory first step
Logging (log-admin-event.sh) — mandatory operation logging
Secrets (secrets CLI) — provider API key retrieval with fallback chain
Profile data (profile.servers[], profile.deployments{}) — server inventory

Sibling Skill Resolution

plugins/admin-devops/
  skills/
    admin/      ← core (scripts, secrets, logging live here)
    devops/     ← this skill (references admin scripts via ../admin/)
    oci/        ← provider skill
    hetzner/    ← provider skill
    ...

Agent Roster

Agent	Model	Role
server-provisioner	sonnet	Cloud VM provisioning via provider CLIs
deployment-coordinator	sonnet	End-to-end app deployment (Coolify/KASM)

Both agents run the profile gate as their first step.

Scripts / References

Provider skills: sibling skills under this plugin (oci, hetzner, coolify, etc.)
Inventory format spec: references/INVENTORY_FORMAT.md
Deployment workflows: references/DEPLOYMENT_WORKFLOWS.md
Troubleshooting: references/TROUBLESHOOTING.md

Comments

Markdown supported

Details

Author: evolv3-ai
Repository: evolv3-ai/vibe-skills
Category: Cloud & DevOps
Installs: 40
GitHub stars: 1

Report

More skills

All skills

lark-apps

open.feishu.cn

746.5k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

wizard

github.com/mattpocock

583.8k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-prepare

github.com/microsoft

575.1k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

azure-ai

github.com/microsoft

574.4k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.