Help developers use Temporal for durable execution workflows. Covers CLI commands, SDK patterns (Go, TypeScript, Python, Java), workflow orchestration, and architectural decisions.
From temporalnpx claudepluginhub rube-de/cc-skills --plugin temporalThis skill is limited to using the following tools:
references/CLI.mdreferences/CONCEPTS.mdreferences/SDK-PATTERNS.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Comprehensive assistance for the Temporal durable execution platform: CLI operations, SDK development across Go/TypeScript/Python/Java, workflow design, and architectural decisions.
Use this skill when the user mentions: "temporal", "durable execution", "workflow orchestration", "temporal cli", "temporal sdk", "temporal worker", "temporal activity", "temporal workflow", "temporal schedule", "temporal signal", "temporal query".
# Install CLI
brew install temporal # macOS
curl -sSf https://temporal.download/cli | sh # Linux
# Start local dev server (with Web UI at localhost:8233)
temporal server start-dev
# Start with persistent storage
temporal server start-dev --db-filename temporal.db
npm init -y
npm install @temporalio/client @temporalio/worker @temporalio/workflow @temporalio/activity
| Developer wants to... | Action |
|---|---|
| Start a workflow | temporal workflow start --type MyWorkflow --task-queue my-queue --input '{"key":"val"}' |
| Check workflow status | temporal workflow describe -w <workflow-id> |
| View event history | temporal workflow show -w <workflow-id> |
| Cancel a workflow | temporal workflow cancel -w <workflow-id> |
| Send a signal | temporal workflow signal -w <workflow-id> --name signal-name --input '{"data":true}' |
| Query workflow state | temporal workflow query -w <workflow-id> --name query-name |
| List running workflows | temporal workflow list |
| Debug stuck workflow | Check history with temporal workflow show, look for pending activities |
| Set up scheduled runs | temporal schedule create --schedule-id my-sched --cron '0 * * * *' ... |
| Test workflows | Use SDK test utilities with time-skipping and activity mocking |
Good fit:
Not a good fit:
For deep dives, consult these references:
| Reference | Content |
|---|---|
| CLI.md | Complete CLI command reference: installation, server, workflows, schedules, operators |
| SDK-PATTERNS.md | Cross-language SDK patterns: Go, TypeScript, Python, Java side-by-side |
| CONCEPTS.md | Architecture, core concepts, design patterns, deployment, comparisons |
Workflows must be deterministic. Common violations:
Date.now(), Math.random(), or system time directly — use workflow.now() or side effectstemporal workflow show -w <id>ActivityTaskScheduled without corresponding ActivityTaskCompletedHeartbeatTimeout for long activitiesTemporal has four timeout types:
If activities time out unexpectedly, ensure StartToCloseTimeout is generous enough and add heartbeating for long-running activities.
TEMPORAL_ADDRESS)When helping with Temporal: