How do I install the Devops Engineer skill?

Run npx skillmds@latest add jochenyang/devops-engineer 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 Devops Engineer safe to use?

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

Which AI agents work with Devops Engineer?

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 Devops Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Devops Engineer?

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

Devops Engineer by jochenyang — Agent Skill

Name: Devops Engineer
Rating: 4.2 (5 reviews)
Author: JochenYang

Devops Engineer

CI/CD pipeline design, containerization, and infrastructure management. Handles Docker, Kubernetes, monitoring setup (Prometheus/Grafana), and infrastructure-as-code (Terraform/Pulumi). Use when user asks to deploy, configure CI/CD, set up Docker/K8s, or manage infrastructure.

JochenYang Updated Sep 10, 2026

File contents

DevOps Engineer

Design and implement CI/CD processes, manage containerized deployments and monitoring/alerting systems.

Core Capabilities

CI/CD pipeline design (GitHub Actions/GitLab CI/Jenkins)
Docker image building and optimization
Kubernetes deployment configuration
Monitoring and alerting system setup (Prometheus/Grafana)
Infrastructure as Code (Terraform/Pulumi)

Operational Research & Communication

Vendor Evaluation: Compare cloud providers, remote access tools, and observability platforms
Security Posture: Assess zero trust frameworks and rollout considerations
Reliability Comms: Draft downtime notices with impact, timing, and contacts
Incident Translation: Explain error logs in business-friendly language

Deployment Strategies

Strategy	Principle	Use Case
Blue-Green	Two environments, instant traffic switch	Stable major releases
Canary Release	Gradually increase new version traffic	High-risk changes
Rolling Update	Replace instances one by one	Kubernetes default

Monitoring Metrics (Golden Signals)

Latency: Response time (P50, P95, P99)
Traffic: Requests per second (RPS)
Errors: Error rate
Saturation: Resource utilization

Boundaries

Focus on CI/CD and infrastructure, not business code development.

When NOT to Use

Writing application code → use developer
Frontend UI development → use frontend-design
API design → use api-designer
Database schema design → use database-engineer
Performance optimization → use performance-optimizer

Detailed References

./references/docker-best-practices.md - Docker optimization guide
./references/kubernetes-patterns.md - Kubernetes best practices

Escalation Rules

Pause and ask the owner before:

making production-facing infrastructure changes without rollback clarity
broadening infra work into unrelated application logic changes
changing secrets, networking, domains, or runtime policies with user-facing impact

Final Output Contract (MANDATORY)

Every use of this skill should end with:

Skill Fit - why DevOps or infra work is appropriate
Primary Deliverable - pipeline, deployment, or infra change summary
Execution Evidence - configs edited, commands run, and checks performed
Risks / Open Questions - rollout, reliability, or security concerns
Next Action - the next safe validation or release step

---name: devops-engineerdescription: CI/CD pipeline design, containerization, and infrastructure management. Handles Docker, Kubernetes, monitoring setup (Prometheus/Grafana), and infrastructure-as-code (Terraform/Pulumi). Use when user asks to deploy, configure CI/CD, set up Docker/K8s, or manage infrastructure.---# DevOps EngineerDesign and implement CI/CD processes, manage containerized deployments and monitoring/alerting systems.## Core Capabilities- CI/CD pipeline design (GitHub Actions/GitLab CI/Jenkins)- Docker image building and optimization- Kubernetes deployment configuration- Monitoring and alerting system setup (Prometheus/Grafana)- Infrastructure as Code (Terraform/Pulumi)## Operational Research & Communication- **Vendor Evaluation**: Compare cloud providers, remote access tools, and observability platforms- **Security Posture**: Assess zero trust frameworks and rollout considerations- **Reliability Comms**: Draft downtime notices with impact, timing, and contacts- **Incident Translation**: Explain error logs in business-friendly language## Deployment Strategies| Strategy | Principle | Use Case ||----------------|------------------------------------------|-----------------------|| Blue-Green | Two environments, instant traffic switch | Stable major releases || Canary Release | Gradually increase new version traffic | High-risk changes || Rolling Update | Replace instances one by one | Kubernetes default |## Monitoring Metrics (Golden Signals)- **Latency**: Response time (P50, P95, P99)- **Traffic**: Requests per second (RPS)- **Errors**: Error rate- **Saturation**: Resource utilization## BoundariesFocus on CI/CD and infrastructure, not business code development.## When NOT to Use- Writing application code → use `developer`- Frontend UI development → use `frontend-design`- API design → use `api-designer`- Database schema design → use `database-engineer`- Performance optimization → use `performance-optimizer`## Detailed References- `./references/docker-best-practices.md` - Docker optimization guide- `./references/kubernetes-patterns.md` - Kubernetes best practices## Escalation RulesPause and ask the owner before:- making production-facing infrastructure changes without rollback clarity- broadening infra work into unrelated application logic changes- changing secrets, networking, domains, or runtime policies with user-facing impact## Final Output Contract (MANDATORY)Every use of this skill should end with:1. `Skill Fit` - why DevOps or infra work is appropriate2. `Primary Deliverable` - pipeline, deployment, or infra change summary3. `Execution Evidence` - configs edited, commands run, and checks performed4. `Risks / Open Questions` - rollout, reliability, or security concerns5. `Next Action` - the next safe validation or release step

Frequently asked questions