Skills

Reviews cloud and AI infrastructure spend to identify measurable savings while preserving reliability, performance, security, ownership, and product requirements.

Designs traces, metrics, structured events, privacy controls, dashboards, and alerts for LLM applications so teams can diagnose quality, cost, latency, and tool-use behavior.

Guides containment, evidence collection, root-cause analysis, customer communication, and remediation when an AI agent takes an unsafe, incorrect, or unauthorized action.

Optimizes prompts and agent workflows for finite context windows by prioritizing evidence, compressing history, managing retrieval budgets, and measuring token-cost trade-offs.

Produces blameless, actionable incident postmortems with a precise timeline, contributing factors, impact, decisions, corrective actions, owners, and measurable follow-through.

Produces production-ready nginx configuration for common scenarios: reverse proxy, load balancing, TLS termination, static file serving, HTTP/2, gzip/brotli, caching, rate limiting, and security headers. Explains each directive, warns about risky defaults, and includes a validation step so the config can be tested before reload.

Writes idempotent Ansible playbooks and roles from a described target state. Structures tasks with proper handlers, variables, and templates; favors modules over shell commands; applies role-based layout and inventory grouping; and adds check-mode safety and tags. Produces playbooks that are re-runnable without unintended side effects.

Produces operational runbooks for services and common incidents. Documents prerequisites, step-by-step diagnosis and remediation, exact commands, verification checks, rollback steps, and escalation paths. Structures each runbook so an on-call engineer can follow it under pressure, and keeps destructive steps clearly flagged with safeguards.

Builds disaster recovery and business continuity plans for systems and data. Defines RTO and RPO targets, maps critical dependencies, chooses backup and replication strategies, documents failover and restore procedures, and designs a testing cadence with game days. Produces a plan that balances resilience against cost and operational complexity.

Designs chaos engineering experiments to validate system resilience. Defines steady-state hypotheses, blast-radius limits, fault injections (latency, errors, instance/zone loss, resource exhaustion), abort conditions, and observability checks. Produces a safe, incremental experiment plan and success criteria for game days and automated chaos.

Adds production-grade observability to a codebase by instrumenting it with structured logs, metrics, and distributed traces. Recommends span boundaries, cardinality-safe labels, and OpenTelemetry conventions, then generates the wiring code and dashboards needed to make a service debuggable in production.

Analyzes cloud spend and produces a FinOps optimization plan. Covers rightsizing, autoscaling, spot/reserved/savings plans, storage tiering, idle resource cleanup, data transfer reduction, and tagging for cost allocation. Prioritizes actions by savings and risk, and defines guardrails and budgets to prevent regressions.

Turns reliability goals into concrete SLIs, SLOs, and error budgets. Helps choose the right service level indicators, set realistic targets from historical data, compute burn rates, and design multi-window multi-burn-rate alerting so teams get paged before the budget is exhausted.

Writes reusable, well-structured Terraform modules with clean input/output interfaces, sensible defaults, validation rules, and examples. Covers module composition, variable typing and validation, remote state and backends, provider version pinning, and testing with terraform validate/plan and tools like Terratest. Emphasizes least-privilege IAM and safe defaults.

Reviews and rewrites Dockerfiles for smaller images, faster builds, and better security. Applies multi-stage builds, optimal layer ordering and caching, minimal base images, non-root users, and .dockerignore tuning, and flags vulnerabilities and bloat while keeping the build reproducible.

Turns incident timelines, alerts, and chat logs into a clear, blameless postmortem. Produces an executive summary, impact assessment, detailed timeline, root-cause analysis using techniques like the five whys, and a prioritized list of follow-up action items with owners, in a format ready to share with stakeholders.

Generates and refactors Helm charts to package Kubernetes applications. Produces templated manifests, values.yaml with sensible defaults, helpers, chart dependencies, and hooks, and parameterizes images, resources, probes, and ingress so a workload can be deployed consistently across environments.

Designs feature-flagging and progressive-delivery strategies and generates the integration code. Covers flag naming and lifecycle, targeting and segmentation rules, percentage rollouts, kill switches, and cleanup of stale flags across providers like LaunchDarkly, Unleash, Flagsmith, or a homegrown config service.

Generates production-ready Kubernetes manifests — Deployments, Services, Ingresses, ConfigMaps, Secrets, HPAs, and more — from a plain-language description of the workload. Applies best practices for resource limits, health probes, security contexts, and rolling update strategies, with optional Kustomize overlays or Helm chart scaffolding.

Parses and analyzes application, system, and access logs to surface errors, anomalies, and root causes. Correlates events across services, identifies recurring patterns and spikes, extracts structured fields from unstructured lines, and produces a prioritized summary with likely causes and recommended next steps.

Generates production-ready infrastructure as code (IaC) configurations for cloud deployments. Supports Terraform, Pulumi, CloudFormation, and CDK. Creates modular, reusable infrastructure components with proper networking, security groups, IAM policies, and monitoring configurations.