Cloud Native Serverless Orchestration
Use when the user asks about AWS Step Functions, Amazon States Language (ASL) state machines, orchestrating Lambdas, Standard vs Express workflows, Distributed Map, Retry/Catch, or a saga with Step Functions. Produces valid ASL with error handling and direct service integrations. Not for Azure Durable Functions (use cloud-native-azure-functions) or Airflow (use data-airflow-dbt-orchestration).
Install
npx skills add j4flmao/agent-skills --skill cloud-native-serverless-orchestrationgit 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/edge-computing/serverless-orchestration ~/.claude/skills/cloud-native-serverless-orchestrationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Serverless Orchestration with AWS Step Functions
## Purpose
Move workflow state, retries, branching, and compensation out of Lambda code into a declarative state machine. Functions stay small and stateless; Step Functions records every transition, so failures are visible and recoverable.
## Agent Protocol
### Trigger
"step functions", "state machine", "amazon states language", "ASL", "orchestrate lambdas", "express workflow", "distributed map", "saga", "retry catch workflow".
### Input Context
- Steps, their side effects, and which are idempotent.
- Duration and volume (executions/s), need for exactly-once vs at-least-once.
- Human approval or external callbacks.
### Output Artifact
ASL definition (JSON) plus IaC wiring. No file unless requested.
### Response Format
```
Workflow type: {Standard|Express (sync|async)} (why)
States: {list}
Error handling: {Retry policies, Catch targets, compensation}
Integrations: {optimized service integrations / Lambda tasks}
```
### Completion Criteria
- [ ] Every Task has Retry for transient errors and Catch for terminal ones.
- [ ] Workflow type chosen from duration/volume/semantics table.
- [ ] Compensating steps defined for any multi-step side effect (saga).
## Standard vs Express
| | Standard | Express |
|---|---|---|
| Max duration | 1 year | 5 minutes |
| Execution semantics | Exactly-once per state transition | At-least-once (async) / at-most-once (sync) |
| Pricing | Per state transition | Per request + duration/memory |Details
- Skill name
cloud-native-serverless-orchestration- Repository
- j4flmao/agent-skills
- Path
skills/cloud-native/edge-computing/serverless-orchestration/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Cloud Native Serverless Orchestration skill do?
Use when the user asks about AWS Step Functions, Amazon States Language (ASL) state machines, orchestrating Lambdas, Standard vs Express workflows, Distributed Map, Retry/Catch, or a saga with Step Functions. Produces valid ASL with error handling and direct service integrations. Not for Azure Durable Functions (use cloud-native-azure-functions) or Airflow (use data-airflow-dbt-orchestration).
How do I install the Cloud Native Serverless Orchestration skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill cloud-native-serverless-orchestration. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cloud Native Serverless Orchestration 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).
Consul
45j4flmao/agent-skills
Use when the user asks about HashiCorp Consul, service discovery, Consul DNS, health checks, Consul KV, ACLs, service mesh intentions, mesh gateways, WAN federation, admin partitions, or consul-template. Produces Consul configs and operations runbooks. Not for Istio or Linkerd (use devops-service-mesh) or Nomad scheduling (use nomad).
Cloud Native Serverless Cold Starts
45j4flmao/agent-skills
Use when the user asks to reduce Lambda cold start latency, Init Duration, provisioned concurrency, SnapStart, GraalVM native Lambdas, Azure Functions or Cloud Run cold starts, or min instances. Produces a measured cold-start diagnosis and fixes for init code, packaging and runtime. Not for Lambda concurrency and event sources (use cloud-native-aws-serverless).
Data Data Observability
45j4flmao/agent-skills
Use when the user asks about data observability: freshness checks, row-count and volume anomalies, schema drift detection, data health dashboards or data incident management with Monte Carlo, Elementary or Soda. Produces monitors, SLAs and incident runbooks across pipeline stages. Not for writing test suites (use data-testing).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.