# Automate Infrastructure and DevOps Operations

Infrastructure work spans many tools, environments, and failure modes. This skill organizes deployment, troubleshooting, automation, monitoring, validation, and documentation into practical workflows.

## Install

```bash
npx skillstore add zl2023github/ops-engineer
```

## Metadata

- Status: approved
- Slug: zl2023github-ops-engineer
- Skillstore revision: r2
- Version status: missing
- Tree hash: 655de688a7589beb25d8f960e2ad7de1b4d72ea89ca8bfe93314764806b1fb95
- Author: zl2023github
- GitHub username: zl2023github
- License: MIT
- Repository: https://github.com/zl2023github/software-engineer-skills/tree/main/software-engineering/ops-engineer
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/zl2023github-ops-engineer
- Manifest: https://skillstore.pages.dev/api/skills/zl2023github-ops-engineer/manifest

## Capabilities

- Creates guidance for Docker, Kubernetes, Helm, Terraform, Ansible, Nginx, and CI/CD configurations.
- Builds troubleshooting workflows for CPU, memory, disk, network, containers, and applications.
- Designs Prometheus collection, Grafana dashboards, logging pipelines, and alert rules.
- Plans backup, disaster recovery, certificate, key rotation, and security baseline tasks.
- Produces change records, incident reports, architecture diagrams, and validation checklists.

## Use Cases

- Standardize Service Deployment: Prepare container, proxy, health-check, validation, and delivery steps for a repeatable service deployment.
- Investigate Production Incidents: Organize read-only system, network, container, and application checks before proposing a controlled fix.
- Build Platform Workflows: Plan Kubernetes resources, CI/CD stages, monitoring, alerts, backups, and operational documentation for an internal platform.

## Prompt Templates

### Plan a Container Deployment

```
Plan a Docker Compose deployment for [service]. Include dependencies, storage, networking, health checks, secrets handling, validation, and rollback. Do not execute commands.
```

### Diagnose High Server Load

```
Help diagnose high load on [server type]. Start with read-only checks for CPU, memory, disk, network, and recent changes. Rank likely causes.
```

### Resolve a Kubernetes Failure

```
Analyze this Kubernetes failure: [symptoms and outputs]. Identify the root cause, propose the smallest change, and define validation. Request approval before changes.
```

### Design a Production Delivery System

```
Design a delivery system for [application and environment]. Cover infrastructure as code, CI/CD, observability, security, backups, failure recovery, approvals, and phased rollout.
```

## Limitations

- Requires access to the target environment and compatible operational tools.
- Does not provide account-specific credentials, policies, architecture details, or production context.
- Generated workflows require review and testing for each operating system, cloud, and application.
- The source does not require confirmation before privileged or production changes.

## Best Practices

- Provide the environment, scope, symptoms, recent changes, constraints, and desired outcome.
- Begin with read-only diagnostics and use dry runs before applying changes.
- Require explicit approval, backups, validation criteria, and rollback steps for production changes.

## Anti Patterns

- Do not place passwords, tokens, private keys, or unredacted secrets in prompts.
- Do not run unreviewed commands with elevated privileges or against production systems.
- Do not skip backups, staged testing, post-change validation, or operational records.

## Security Audit

- Audited at: 2026-07-23T23:45:34.527\+00:00
- Summary: All 20 static findings are false positives caused by Markdown fences, inline code formatting, Chinese text, or legitimate operational terminology. The file contains readable guidance, not obfuscated content, executable backticks, privilege-escalation commands, or malicious reconnaissance. However, the skill authorizes broad operational execution without mandatory approval and rollback safeguards, creating a high-impact change risk.

## Stats

- Views: 1
- Downloads: 5
- Favorites: 0
- Popularity score: 0