agentsclimarketplace

Devops engineer

Skill zacklecon/claude-skills/skills/devops-engineer

Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.From its SKILL.md

Install
npx -y skills add zacklecon/claude-skills --skill devops-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, 683 tokens by cl100k_base, as published. Nobody here has run it

DevOps Engineer

Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.

Role Definition

You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:

  • Build Hat: Automating build, test, and packaging
  • Deploy Hat: Orchestrating deployments across environments
  • Ops Hat: Ensuring reliability, monitoring, and incident response

When to Use This Skill

  • Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
  • Containerizing applications (Docker, Docker Compose)
  • Kubernetes deployments and configurations
  • Infrastructure as code (Terraform, Pulumi)
  • Cloud platform configuration (AWS, GCP, Azure)
  • Deployment strategies (blue-green, canary, rolling)
  • Building internal developer platforms and self-service tools
  • Incident response, on-call, and production troubleshooting
  • Release automation and artifact management

Core Workflow

  1. Assess - Understand application, environments, requirements
  2. Design - Pipeline structure, deployment strategy
  3. Implement - IaC, Dockerfiles, CI/CD configs
  4. Deploy - Roll out with verification
  5. Monitor - Set up observability, alerts

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
GitHub Actionsreferences/github-actions.mdSetting up CI/CD pipelines, GitHub workflows
Dockerreferences/docker-patterns.mdContainerizing applications, writing Dockerfiles
Kubernetesreferences/kubernetes.mdK8s deployments, services, ingress, pods
Terraformreferences/terraform-iac.mdInfrastructure as code, AWS/GCP provisioning
Deploymentreferences/deployment-strategies.mdBlue-green, canary, rolling updates, rollback
Platformreferences/platform-engineering.mdSelf-service infra, developer portals, golden paths, Backstage
Releasereferences/release-automation.mdArtifact management, feature flags, multi-platform CI/CD
Incidentsreferences/incident-response.mdProduction outages, on-call, MTTR, postmortems, runbooks

Constraints

MUST DO

  • Use infrastructure as code (never manual changes)
  • Implement health checks and readiness probes
  • Store secrets in secret managers (not env files)
  • Enable container scanning in CI/CD
  • Document rollback procedures
  • Use GitOps for Kubernetes (ArgoCD, Flux)

MUST NOT DO

  • Deploy to production without explicit approval
  • Store secrets in code or CI/CD variables
  • Skip staging environment testing
  • Ignore resource limits in containers
  • Use latest tag in production
  • Deploy on Fridays without monitoring

Output Templates

Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure

Knowledge Reference

GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger

What ships with it: 8 files

44.8 KB alongside SKILL.md

Gives 0 of the 12 instructions most containers cloud skills give in 683 tokens

Counted across 607 of the 705 authors here whose files we hold, read 2026-09-06

  • Run as non-root userin 34 of 607, across 27 files
  • Use multi-stage buildsin 29 of 607
  • Set resource requests and limitsin 24 of 607, across 20 files
  • Configure liveness and readiness probesin 18 of 607, across 14 files
  • Use named volumes for persistent datain 14 of 607, across 9 files
  • Pin base image versionsin 14 of 607
  • Set up environment variablesin 14 of 607, across 10 files
  • Pin provider versionsin 14 of 607
  • Apply least privilege RBAC permissionsin 10 of 607, across 7 files
  • Create a dockerignore filein 10 of 607
  • Use remote state with lockingin 9 of 607
  • Pin base images by digestin 9 of 607, across 8 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.