temporal-developer

Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or Temporal Cloud, or working with durable execution concepts like signals, queries, heartbeats, versioning, continue-as-new, child workflows, or saga patterns. Also use when the user me

183stars22forksUpdated 6/19/2026

Developer Tools #microservices #backend-development #temporal #distributed-systems #workflow-orchestration #durable-execution

Security Assessment

Critical Risk(10/100)

Detected risks:

Secret Exposure([references/dotnet/gotchas.md] Token =, [references/dotnet/patterns.md] Token =, [references/dotnet/advanced-features.md] Token =)

Sensitive File Access([references/python/standalone-activities.md] .env, [references/go/testing.md] .env, [references/python/versioning.md] .env)

Privilege Escalation([references/core/priority-fairness.md] RunAs, [references/dotnet/dotnet.md] RunAs, [references/dotnet/gotchas.md] RunAs)

Security Score10/100

About temporal-developer

The temporal-developer skill provides comprehensive guidance for building, debugging, and managing Temporal applications across seven programming languages: Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Temporal is a durable execution platform that ensures workflows survive failures automatically through history replay and event sourcing. This skill helps developers work with the Temporal architecture, including the Temporal Cluster (Event History, Task Queues, and Visibility store), Workers that execute workflow and activity code, and the three deployment options: local dev server, self-hosted clusters, and Temporal Cloud.

The skill covers core Temporal concepts including workflow definitions (deterministic orchestration functions), activity implementations (non-deterministic operations with retry logic), and the critical concept of determinism required for history replay. It provides guidance on using Temporal CLI commands for workflow management (start, execute, signal, query, update), debugging common issues like non-determinism errors, stuck workflows, and activity retries, and implementing advanced patterns like signals, queries, heartbeats, versioning, continue-as-new, child workflows, and saga patterns. The skill ensures developers understand why determinism matters and how Commands must match Events during replay to prevent workflow failures.

This skill is essential for backend engineers and platform developers building resilient distributed systems, microservices orchestration, long-running business processes, data pipelines, or any application requiring durable execution guarantees. It's particularly valuable for teams migrating from traditional job queues or state machines to Temporal's durable execution model, developers troubleshooting workflow failures in production, and engineers setting up local development environments or production Temporal deployments.

FAQ

Which programming languages does this skill support?

This skill supports seven languages: Python, TypeScript, Go, Java, .NET (C#), Ruby, and Rust. Each language has dedicated reference documentation for getting started with Temporal SDK implementation.

What's the difference between the Temporal dev server, self-hosted, and Temporal Cloud?

The Temporal CLI dev server is a single-process local server started with 'temporal server start-dev', suitable only for development and testing. Self-hosted deployments require you to manage the Temporal server and its dependencies (like databases) in your own infrastructure for production use. Temporal Cloud is a fully managed production service with no cluster infrastructure to manage.

Why does my workflow fail with a non-determinism error?

Non-determinism errors occur when Commands generated during workflow replay don't match the stored Events in the history. This happens when workflow code changes produce different execution paths (e.g., changing the order of activities, adding new activities before existing ones, or using non-deterministic operations like random numbers or current time directly in workflow code). The workflow becomes blocked because Temporal cannot safely reconstruct its state.

What's the difference between workflows and activities?

Workflows are deterministic orchestration functions that must not have side effects and survive failures through history replay. Activities are non-deterministic operations (API calls, database queries, file I/O) that can fail and be retried automatically. Workflows coordinate activities but should never directly perform I/O or external calls.

Do I need to install Temporal CLI to use this skill?

Yes, the Temporal CLI is required for running the local dev server, starting workflows, sending signals/queries, and managing Temporal resources. The skill includes instructions for checking if it's installed and references for installing it on your platform.

All Files

100 files

SKILL.md7.4 KB