Cloud Native Event Driven Scaling
Use when the user asks about KEDA, ScaledObject, ScaledJob, TriggerAuthentication, scale to zero, scaling pods on queue length, Kafka consumer lag or SQS depth autoscaling on Kubernetes. Produces KEDA configs with flapping control and long-running job handling. Not for CPU/memory HPA, VPA or node autoscaling (use devops-kubernetes-autoscaling).
Install
npx skills add j4flmao/agent-skills --skill cloud-native-event-driven-scalinggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/cloud-native/event-driven-scaling ~/.claude/skills/cloud-native-event-driven-scalingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event-Driven Scaling with KEDA
## Purpose
CPU-based HPA reacts late to queue backlogs and cannot scale from zero. KEDA feeds event-source metrics to the HPA and handles 0↔1 activation itself, so consumers scale with work waiting rather than with CPU after the fact.
## Agent Protocol
### Trigger
"keda", "scale to zero", "ScaledObject", "ScaledJob", "scale on queue length", "kafka consumer autoscaling", "sqs scaling", "event driven autoscaling", "TriggerAuthentication".
### Input Context
- Event source and auth model (IRSA/EKS Pod Identity, Workload Identity, secrets).
- Per-pod throughput (messages/s) and acceptable backlog drain time.
- Message processing duration (seconds vs hours).
### Output Artifact
`ScaledObject`/`ScaledJob` + `TriggerAuthentication` YAML. No file unless requested.
### Response Format
```
Resource: {ScaledObject|ScaledJob} (why)
Trigger: {type} target={value} activation={value}
Replicas: min={n} max={n} (max bounded by {partitions|downstream limit})
Flapping control: {cooldownPeriod, HPA behavior}
Auth: {TriggerAuthentication / ClusterTriggerAuthentication}
```
### Completion Criteria
- [ ] Target value derived from per-pod throughput, not guessed.
- [ ] `maxReplicaCount` bounded by partitions or downstream capacity.
- [ ] Long-running work uses ScaledJob or graceful termination.
## How KEDA WorksDetails
- Skill name
cloud-native-event-driven-scaling- Repository
- j4flmao/agent-skills
- Path
skills/cloud-native/event-driven-scaling/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Cloud Native Event Driven Scaling skill do?
Use when the user asks about KEDA, ScaledObject, ScaledJob, TriggerAuthentication, scale to zero, scaling pods on queue length, Kafka consumer lag or SQS depth autoscaling on Kubernetes. Produces KEDA configs with flapping control and long-running job handling. Not for CPU/memory HPA, VPA or node autoscaling (use devops-kubernetes-autoscaling).
How do I install the Cloud Native Event Driven Scaling skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill cloud-native-event-driven-scaling. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cloud Native Event Driven Scaling popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Cloud Native Kubernetes Mastery
45j4flmao/agent-skills
Use when the user asks for a production-ready Helm chart, Helm template helpers, values.schema.json, chart tests, a kubebuilder scaffold, or writing a Kubernetes operator in Go next to a chart. Produces an upgrade-safe chart plus an operator skeleton. Not for operator lifecycle and OLM (use devops-kubernetes-operators) or helmfile releases (use helm-patterns).
Cloud Native Ebpf Observability
45j4flmao/agent-skills
Use when the user asks about bpftrace, tracing syscalls, kprobes, tracepoints, uprobes, off-CPU or continuous profiling with eBPF, libbpf ring buffers, or measuring kernel latency. Produces bpftrace one-liners and libbpf CO-RE agents, and picks tools like Parca, Pixie, Tetragon or Beyla. Not for packet processing (use cloud-native-ebpf-networking) or threat detection (use ebpf-threat-detection).
Cloud Native Kubernetes Patterns
45j4flmao/agent-skills
Use when the user asks about sidecar or native sidecar containers, ambassador/adapter/init patterns, PodDisruptionBudget, topology spread, pod anti-affinity, taints and tolerations, graceful shutdown, or ValidatingAdmissionPolicy. Produces current-API workload YAML. Not for control-plane internals (use kubernetes-internals) or autoscaling (use devops-kubernetes-autoscaling).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.