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 mentions "run a Temporal workflow from the CLI", "start a dev server", "run temporal server start-dev", "temporal workflow start", "temporal workflow execute", "temporal workflow signal", "temporal workflow query", "temporal workflow update".
84
—
Does it follow best practices?
Impact
97%
1.90xAverage score across 3 eval scenarios
Passed
No known issues
Python project structure, sync activities, heartbeating, large data via references
Separate workflow files
100%
100%
Separate activity files
100%
100%
Sandbox-safe activity import
100%
100%
Sync activities used
0%
100%
Executor for sync activities
0%
100%
References passed, not large data
100%
100%
Activity heartbeating
100%
100%
Heartbeat details recovery
100%
100%
Cancellation cleanup with try/finally
50%
20%
workflow.logger used in workflow
100%
100%
Multi-tenant fairness, update validators, query handlers, state in __init__
Fairness key on workflow start
0%
100%
Fairness weight set
0%
100%
State initialized in __init__
83%
100%
Update handler returns count
10%
100%
Update validator is read-only
0%
100%
Validator rejects empty items
37%
100%
Validator rejects over-capacity
37%
100%
Query handler is read-only
100%
100%
Fairness explained in comments
50%
100%
Priority import used
0%
100%
Saga compensation ordering, patching API, deterministic time/UUID/sleep
Compensation added before activity
0%
100%
Compensations run in reverse
100%
100%
asyncio.shield used for compensations
0%
100%
Patching API used for new step
100%
100%
Descriptive patch ID
100%
100%
workflow.now() for timestamp
0%
100%
workflow.uuid4() or workflow.random() for unique ID
0%
100%
workflow.sleep() for durable delay
100%
100%
CHANGES.md explains patching lifecycle
100%
100%
Compensation activities are idempotent by design
0%
100%
e7b111c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.