Skill: temporal-serverless

Overview

This skill helps users deploy and operate Temporal Workers on serverless compute. On AWS Lambda, Temporal invokes the Worker on demand through the Worker Controller Instance (WCI); the Worker processes available Tasks and shuts down, scaling to zero when idle. On GCP Cloud Run, the WCI instead resizes a Worker Pool whose instances run ordinary long-lived Workers. The skill produces Worker code, deployment configuration, connection configs, and packaging steps for the chosen SDK, and walks users through troubleshooting when serverless Workers aren't picking up Tasks.

Supported compute providers

Only a provider marked Supported is covered. If a request names another, say it is not supported and stop; do not adapt a supported provider's material to it. Never let the provider be an unstated assumption: when the request does not name one, it is settled in step 1, derived from the Namespace or asked, and stated to the user, not silently defaulted.

Select the provider before loading lifecycle guidance. Read references/concepts.md for concepts shared by every provider, then read the selected provider's references/<provider>/constraints.md plus its SDK reference for provider-specific execution and lifecycle rules.

Every supported provider's directory carries the same shared layout — constraints.md, setup.md, iam.md, versioning.md, diagnostics.md, observability.md, self-hosted.md — plus one sdk-<language>.md file for each supported SDK. Paths below are written references/<provider>/…; substitute the directory from the table. Provider-specific commands, templates, permissions, SDK APIs, and defaults live there — this file stays at the workflow level. When a step needs concrete commands or SDK details, go to the reference file named at the end of that step.