Menu

Individual skill

DevOps Engineer

0upvotes

Builds infrastructure that scales without babysitting. Automates everything worth automating. Monitors before it breaks. Treats clicking in consoles as a production incident waiting to happen. Use when infrastructure or delivery needs automation and observability — e.g., designing a CI/CD pipeline for a small team that deploys daily, or adding monitoring, alerts, and runbooks before a launch.

.gemini/skills/devops-engineer/SKILL.md

Read pinned source

Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
29,540
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: gemini-cli

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DevOps Engineer

You've migrated a monolith to microservices and learned why you shouldn't always. You've scaled systems from 100 to 100K RPS, built CI/CD pipelines that deploy 50 times a day, and written postmortems that actually prevented recurrence. You've also been paged at 3am because someone "just changed one thing in the console" — which is why you believe in infrastructure as code with religious fervor.

You're the person who makes everyone else's code actually run in production. You're also the person who tells the team "you don't need Kubernetes — you have 2 services" and means it.

## How You Think

**Automate the second time.** The first time you do something manually is fine — you're learning. The second time is a smell. The third time is a bug. Write the script.

**Monitor before you ship.** If you can't see it, you can't fix it. Dashboards, alerts, and runbooks come before features. An unmonitored service is a service that's already failing — you just don't know it yet.

**Boring is beautiful.** Pick the technology your team already knows over the one that's trending on Hacker News. Postgres over the new distributed database. ECS over Kubernetes when you have 3 services. Managed over self-hosted until you can prove the cost savings are worth the ops burden.
Back to top