ops-engineer

Executes CMDB environment deployment, backup, restore, and troubleshooting runbooks across docker-compose and Kubernetes.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill ops-engineer-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-engineer
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/roles/ops-engineer
Command: npx skills add https://github.com/lfuuu/claude-rules --skill ops-engineer-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating CMDB environments (dev/test/stage/loadtest via docker-compose and production Kubernetes clusters via kube_ci) requires strict, error-prone operational procedures where improvisation can cause production data loss. This Skill acts as a pure runbook executor that deploys, backs up, restores, and troubleshoots environments without ever modifying code, configs, or scripts. ## Core Features & Use Cases - Environment lifecycle management: Setup, deploy, backup, restore, and troubleshoot docker-compose environments (dev/test/stage/loadtest) through the cmdb-env.sh script with mandatory healthchecks. - Kubernetes production operations: Deploy, redeploy, dismiss, backup, and restore CMDB instances (prod-adp2, prod-testop, preprod targets) exclusively through kube_ci pipeline scripts on the KVM host, with enforced backup and architect confirmation before destructive production actions. - Production safety guardrails: Hard NEVER rules prevent direct kubectl apply/helm install, namespace deletion without backup, scp of repo files, and any file modification, with explicit escalation paths to other roles. - Use Case: Run a full production redeploy of the prod-adp2 CMDB instance: the Skill resolves the target, takes a pg_dump backup, asks for architect confirmation, deletes the namespace, redeploys via kube_ci, and verifies health and login. ## Quick Start Ask the agent to deploy the stage environment or run a Kubernetes backup of prod-adp2, for example by invoking the ops-engineer skill with the argument "deploy stage" or "k8s-backup prod-adp2".

Frequently Asked Questions about ops-engineer

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

FAQPage Schema
How do I deploy a CMDB environment with docker-compose?

Invoke the skill with a command like "setup dev" or "deploy stage". It runs scripts/cmdb-env.sh with the environment and command, verifies passwords are not CHANGE_ME on stage, and checks the healthcheck endpoint after startup.

How do I deploy CMDB to a production Kubernetes cluster?

Use the k8s-deploy command with a target such as prod-adp2 or prod-testop. The skill resolves the target to its kube_ci directory, context, and product key, then runs 00-build-deploy.sh over SSH on the KVM host. Direct kubectl apply or helm install is forbidden.

Can this skill modify scripts, configs, or application code?

No. It is a pure runbook executor and is forbidden from using Edit, Write, or NotebookEdit tools. If a script or config is wrong, it stops and escalates to the responsible role such as devops, backend, or techwriter.

What happens before destructive operations on production Kubernetes?

Before deleting a namespace, redeploying, or dismissing a prod instance, the skill takes a pg_dump backup via kubectl exec and asks the architect for explicit confirmation naming the target organization. The two prod instances are isolated per namespace.

How do I back up and restore a CMDB database in Kubernetes?

Run k8s-backup with a target to produce a gzipped pg_dumpall file on the KVM host, and k8s-restore with the target and backup file to restore it. Restore to prod instances requires the --allow-prod flag and is treated as disaster recovery.

Why does the skill refuse to run kubectl apply or helm upgrade directly?

All Kubernetes changes must go through kube_ci pipeline scripts (00-build-deploy.sh, 01-dissmiss.sh) so deployments stay reproducible through werf. kubectl is allowed only for diagnostics like get, logs, describe, and specific runbook-defined pod deletions.