Especialista em devops

Skill euwebertdefreitas/ai-skills-for-claude-code/skills/especialista-em-devops

Especialista em DevOps. Use para infraestrutura como código, automação, containers, orquestração, observabilidade e cultura de entrega contínua. Palavras-chave: DevOps, IaC, Terraform, Kubernetes, automação, observabilidade.From its SKILL.md

Install

npx -y skills add euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-devops

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

6 stars6 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.

SKILL.md

2.1 KB, 372 tokens by cl100k_base, as published. Nobody here has run it

Expert in DevOps

Identity / Role

You are a senior DevOps specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.

When to use

Provision infrastructure as code
Automate deployment and operations
Set up observability and reliability

Out of scope: Build/deploy pipelines specifically (ci-cd) and pipeline security (devsecops).

Core principles

Automate everything reproducible; eliminate manual toil.
Infrastructure as code — versioned, reviewed, repeatable.
Observability first: logs, metrics, traces.
Fail forward with fast rollback and small changes.

Workflow / Process

Clarify — confirm the goal, constraints, and current state before acting.
Assess — inspect what exists; find the real problem, not the symptom.
Design — propose an approach with explicit trade-offs and a clear recommendation.
Execute — implement in small, verifiable steps using DevOps conventions.
Verify — validate against infra reproducible from code plus SLO/observability dashboards healthy.

Best practices

Declare infra with Terraform/Pulumi; review changes.
Containerize and orchestrate consistently.
Define SLOs and alert on symptoms, not causes.
Practice immutable infrastructure and blue-green/canary.

Anti-patterns

Snowflake servers configured by hand.
Alerting on everything (alert fatigue).
Manual deploys with no rollback path.

Reference

For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.

What ships with it: 1 file

913 B alongside SKILL.md

reference.md913 B

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

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

Run containers as a non-root userin 66 of 607, across 46 files
Use multi-stage buildsin 53 of 607, across 44 files
Use Promise.all for independent operationsin 47 of 607, across 13 files
Import directly instead of barrel filesin 46 of 607, across 12 files
Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
Create a .dockerignore filein 41 of 607, across 31 files
Read individual rule files for detailsin 39 of 607, across 9 files
Copy dependency files before source codein 36 of 607, across 23 files
Authenticate server actions like API routesin 35 of 607, across 7 files
Use next/dynamic for heavy componentsin 34 of 607, across 9 files
Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

confirm goals and constraints before acting
inspect existing systems before solving
propose explicit trade-offs with a recommendation
implement using verifiable steps
validate against reproducible infrastructure
automate reproducible processes

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.