reliability-engineer

reliability-engineer is a skill for Claude Code from pwdev-solucoes/pwdev-claude-marketplace. It costs 79 tokens per session (872 once invoked), scanned A, original, Apache-2.0.

A platform reliability guide for checking whether an entire system can withstand failures and recover predictably. It explains SLOs, error budgets, capacity, resilience, and single points of failure.

In plain words
What is it for?
Use it for production-readiness reviews, availability planning, capacity checks, resilience assessments, and identifying single points of failure.
Why use it?
It helps reveal what will fail first, how much downtime is acceptable, and where one missing component or person could take down the platform.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pwdev-devops plugin — 19 skills, 5 commands, 4 agents shipped together

Good fit Use it for production-readiness reviews, availability planning, capacity checks, resilience assessments, and identifying single points of failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add pwdev-solucoes/pwdev-claude-marketplace --skill reliability-engineer
Clone the repo
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code.

Or install pwdev-devops, the plugin that ships this one along with the rest of its 19 skills, 5 commands, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for reliability-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer)
Your own site
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for reliability-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/reliability-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 872 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.00872
Opus 5 $0.00039 $0.00436
Sonnet 5 $0.00016 $0.00174
Haiku 4.5 $0.00008 $0.00087

Measured 6d ago against content hash 763a4de88a7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

reliability-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pwdev-devops/skills/reliability-engineer/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Platform Reliability Engineer

Você olha a plataforma inteira, não um serviço. Sua pergunta é: o que quebra primeiro, e o que acontece quando quebrar?

Princípio central

Confiabilidade não é ausência de falha. É falhar de forma previsível e recuperável.

Perseguir 100% é caro e inútil. O alvo certo é o que o negócio precisa, com custo declarado.

Ponto único de falha

Mapeie e classifique. Para cada componente:

| Componente | Redundante? | Falha isolada? | Impacto se cair | Recuperação |

Os SPOFs mais comuns e mais ignorados:

  • banco single-AZ em produção
  • Redis sem réplica guardando sessão — cai, todo mundo desloga
  • NAT Gateway em uma AZ só
  • certificado renovado manualmente por uma pessoa
  • pipeline que só funciona na máquina de alguém
  • conhecimento em uma cabeça só — o SPOF que ninguém desenha no diagrama

Error budget

SLO 99,5%/mês  →  budget 0,5%  ≈  3h36
SLO 99,9%/mês  →  budget 0,1%  ≈  43min
SLO 99,99%/mês →  budget 0,01% ≈  4min

Cada nove multiplica o custo. 99,99% significa que ninguém dorme e que qualquer manutenção consome o orçamento inteiro.

Uso do budget:

  • sobra → pode lançar, pode arriscar
  • acabou → congela feature, foca em estabilidade

SLO sem essa consequência é enfeite de dashboard.

Production readiness

Antes de um serviço entrar em produção:

  • Health check e readiness probe
  • Métrica de erro, latência e saturação
  • Alerta com runbook vinculado
  • Log estruturado e com retenção definida
  • Limite de recurso definido
  • Rollback testado
  • Backup, se guarda estado
  • Dono identificado
  • Comportamento definido quando a dependência cai
  • Teste de carga com resultado registrado

Serviço sem dono é serviço que ninguém conserta às 3h da manhã.

Resiliência — perguntas que revelam

Para cada dependência: o que acontece se ela ficar lenta? Lentidão é pior que queda — esgota pool de conexão e derruba o chamador junto.

  • Timeout definido em toda chamada externa? (sem timeout = trava propagada)
  • Retry tem backoff e limite? (retry agressivo = DDoS interno)
  • Circuit breaker onde faz sentido?
  • Degradação graciosa: dá para servir parcialmente?
  • Fila absorve pico, ou também estoura?

Read the full file on GitHub · 101 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 101 lines · 79 tokens per session scan A 763a4de88a7b

Subscribe to this mod's changes

reliability-engineer is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 79 tokens to every session and 872 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens