Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
Install Temporal Developer
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install temporalio/skill-temporal-developer temporal-developer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
Claude Code skills documentation · loads skills from .claude/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .claude/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install temporalio/skill-temporal-developer temporal-developer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .agents/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install temporalio/skill-temporal-developer temporal-developer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .cursor/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install temporalio/skill-temporal-developer temporal-developer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .gemini/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install temporalio/skill-temporal-developer temporal-developerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .github/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install temporalio/skill-temporal-developer temporal-developer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "temporal-developer" agent skill from https://github.com/temporalio/skill-temporal-developer/tree/main into .opencode/skills/temporal-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temporal-developer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
temporal-developer- GitHub stars
- 230
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,014 words
- Files
- 135 (incl. references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
- Works in 4 steps: Initial Execution - Worker runs… → Recovery - On restart/failure, Worker… → Matching - SDK compares generated… → …
- The user is building workflows
- SKILL.md covers Overview, Out of Scope, Core Architecture and History Replay: Why…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Temporal Developer is an agent skill from temporalio/skill-temporal-developer, published by the product's own GitHub organization. Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, workers, or background job queues 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…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 138 other files, including reference files (for example `.github/workflows/ci.yml`, `CONTRIBUTING.md` and `README.md`).
It sits in Backend & APIs, covering Background jobs, Microservices and Debugging. It works with Temporal, Java, Python and Ruby. The repository describes itself as: Comprehensive Skill for developing with Temporal. The licence is MIT.
When your agent uses it
- The user is building workflows
- Background job queues with a Temporal SDK
- Debugging issues like non-determinism errors
- Stuck workflows
Example prompts
- “run a Temporal workflow from the CLI”
- “start a dev server”
- “run temporal server start-dev”
- “/temporal-developer”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Initial Execution - Worker runs workflow, generates Commands, stored as Events in history
- Recovery - On restart/failure, Worker re-executes workflow from beginning
- Matching - SDK compares generated Commands against stored Events
- Restoration - Uses stored Activity results instead of re-executing
What it can do on your machine
Read from SKILL.md and the folder at commit 133fa1d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Temporal Developer loads about 2.5k tokens when it runs, and up to ~213k if it reads all its reference files. Until then it costs about 196 tokens; SKILL.md has 1,014 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from temporalio/skill-temporal-developer at commit 133fa1d, republished under its MIT licence (© temporalio). 1,014 words, ~2,469 tokens.
Download SKILL.mdSave it as
.claude/skills/temporal-developer/SKILL.md (or your agent's skills folder). This skill also uses 134 other files; get the full folder from GitHub.- name
- temporal-developer
- description
- Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, workers, or background job queues 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".
Skill: temporal-developer
Overview
Temporal is a durable execution platform that makes workflows survive failures automatically. This skill provides guidance for building Temporal applications in Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
Out of Scope
- Operational CLI commands such as batch operations, health queries, Cloud administration,
tcld, and scripting → use the temporal-ops skill. - Serverless Worker deployment and troubleshooting → use the temporal-serverless skill.
- First-time Temporal Cloud setup including a Namespace, API key, sample app, and first Workflow → use the temporal-cloud-setup skill.
If a task shifts into one of these areas, follow the relevant skill. Local development and developer-facing Workflow CLI commands remain covered here.
Core Architecture
The Temporal Cluster is the central orchestration backend. It maintains three key subsystems: the Event History (a durable log of all workflow state), Task Queues (which route work to the right workers), and a Visibility store (for searching and listing workflows). There are three ways to run a Cluster:
- Temporal CLI dev server — a local, single-process server started with
temporal server start-dev. Suitable for development and testing only, not production. - Self-hosted — you deploy and manage the Temporal server and its dependencies (e.g., database) in your own infrastructure for production use.
- Temporal Cloud — a fully managed production service operated by Temporal. No cluster infrastructure to manage.
Workers are long-running processes that you run and manage. They poll Task Queues for work and execute your code. You might run a single Worker process on one machine during development, or run many Worker processes across a large fleet of machines in production. Each Worker hosts two types of code:
- Workflow Definitions — durable, deterministic functions that orchestrate work. These must not have side effects.
- Activity Implementations — non-deterministic operations (API calls, file I/O, etc.) that can fail and be retried.
Workers communicate with the Cluster via a poll/complete loop: they poll a Task Queue for tasks, execute the corresponding Workflow or Activity code, and report results back.
History Replay: Why Determinism Matters
Temporal achieves durability through history replay:
- Initial Execution - Worker runs workflow, generates Commands, stored as Events in history
- Recovery - On restart/failure, Worker re-executes workflow from beginning
- Matching - SDK compares generated Commands against stored Events
- Restoration - Uses stored Activity results instead of re-executing
If Commands don't match Events = Non-determinism Error = Workflow blocked
See Commands and Events for a table showing how Workflow actions are recorded in Event History.
Choose References for the Task
Identify the SDK language and the developer's task. Read the relevant core reference in the section below and its language-specific counterpart when available. Load additional references only as the task requires.
For a new project, a first implementation, or broad SDK guidance, read the appropriate SDK guide:
- Python -> Python SDK guide
- TypeScript -> TypeScript SDK guide
- Go -> Go SDK guide
- Java -> Java SDK guide
- .NET (C#) -> .NET SDK guide
- Ruby -> Ruby SDK guide
- Rust -> Rust SDK guide (in Public Preview)
For tasks that use Temporal CLI or start a local dev server, check whether temporal is installed before using it. If it is missing, follow the Temporal CLI installation guide.
Show full SKILL.md (507 more words)Show less
Primary References
- Temporal determinism rules - Why determinism matters, replay mechanics, basic concepts of activities
- Language-specific info at
references/{your_language}/determinism.md
- Language-specific info at
- Temporal workflow determinism protection - SDK safeguards, analyzers, runtime checks, and their limits
- Language-specific info at
references/{your_language}/determinism-protection.md
- Language-specific info at
- Temporal workflow patterns - Conceptual patterns (signals, queries, saga)
- Language-specific info at
references/{your_language}/patterns.md
- Language-specific info at
- Temporal common pitfalls - Anti-patterns and common mistakes
- Language-specific info at
references/{your_language}/gotchas.md
- Language-specific info at
- Temporal versioning guide - Versioning strategies and concepts - how to safely change workflow code while workflows are running
- Language-specific info at
references/{your_language}/versioning.md
- Language-specific info at
- Temporal standalone Activities guide - Standalone Activities: run an Activity directly from a Client without a Workflow — Temporal's job queue
- Language-specific info at
references/{your_language}/standalone-activities.md
- Language-specific info at
- Temporal Task Queue priority and fairness guide - Task Queue Priority and Fairness concepts, configuration, and limitations
- Language-specific info at
references/{your_language}/priority-fairness.md
- Language-specific info at
- Temporal Workflow random streams guide - SDK-provided named deterministic random streams for Workflow code, plugins, and interceptors
- Language-specific info at
references/{your_language}/random-streams.md(Go and TypeScript)
- Language-specific info at
- Temporal troubleshooting guide - Decision trees, recovery procedures
- Temporal error reference - Common error types, workflow status reference
- Temporal interactive workflow guide - Testing signals, updates, queries
- Temporal development management guide - Dev cycle & management of server and workers
- Temporal CLI workflow command guide - Developer-facing CLI commands for workflow interaction (start, execute, signal, query, update, cancel)
- Temporal AI integration patterns - AI/LLM pattern concepts
- Language-specific info at
references/{your_language}/ai-patterns.md, if available. Currently Python only.
- Language-specific info at
Job Queues and Background Jobs
Temporal's job queue is Standalone Activities. When the developer asks for a job queue, background or async jobs, a work queue, or whether Temporal can replace Celery, Sidekiq, BullMQ, Resque, Hangfire, or SQS-plus-workers, build it with a Standalone Activity — not a Workflow wrapping a single Activity, and not a dispatcher Workflow that receives jobs by Signal.
Temporal Task Queues are the routing mechanism Workers poll, not a queue that producers push jobs into. Do not answer a job queue question by describing Temporal Task Queues.
When a developer says "task queue" they may mean "job queue": Celery, Dramatiq, Huey, and Asynq all use Task nomenclature, while Sidekiq, Hangfire, BullMQ, Resque, RQ, and Faktory use Job. Read "can I use Temporal as a task queue?" as a job queue question, and reserve Temporal's Task Queue meaning for your own reply.
- Temporal job queue guide - Job-queue vocabulary mapped to Temporal, migrating off an existing job queue, anti-patterns, and per-language SDK guides and runnable samples
Additional Topics
references/{your_language}/observability.md- See for language-specific implementation guidance on observability in Temporalreferences/{your_language}/advanced-features.md- See for language-specific guidance on advanced Temporal features and language-specific features
Third-Party Integrations
For Temporal plugins and integrations with third-party frameworks and SDKs (Spring Boot, Spring AI, OpenAI Agents SDK, Google ADK, etc.), see integrations catalog — a single catalog table with the language, what each integration does, and a pointer to its reference file under references/{language}/integrations/.
Feedback
Reporting Issues in This Skill
If you (the AI) find this skill's explanations are unclear, misleading, or missing important information—or if Temporal concepts are proving unexpectedly difficult to work with—draft a GitHub issue body describing the problem encountered and what would have helped, then ask the user to file it at https://github.com/temporalio/skill-temporal-developer/issues/new. Do not file the issue autonomously.
© temporalio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 134 other files (references) in the repository root of temporalio/skill-temporal-developer.
- SKILL.md
- .github/CODEOWNERS
- .github/workflows/ci.yml
- .gitignore
- CONTRIBUTING.md
- LICENSE
- README.md
- pyproject.toml
- references/core/ai-patterns.md
- references/core/cli-workflow-commands.md
- references/core/determinism.md
- references/core/dev-management.md
- references/core/error-reference.md
- references/core/gotchas.md
- references/core/install_cli.md
- references/core/interactive-workflows.md
- references/core/job-queue.md
- … and 118 more
Open the folder on GitHubat commit 133fa1d
Compare with similar skills
Temporal Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Temporal Developer this skilltemporalio/skill-temporal-developer | 230 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Dbgtheodo-group/debug-that | 158 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Supercovsupercorp-ai/supercov | 148 | 1 repos | ~415 | Automated safety check: Pass | MIT | |
| Security Reviewgithub/awesome-copilot | 40k | 1 repos | ~2.3k | Automated safety check: Notes | MIT | |
| Temporal Developerlatitude-dev/latitude-llm | 4.7k | — | ~1.5k | Automated safety check: Pass | MIT | |
| K8e Sandboxxiaods/k8e | 499 | — | ~6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Supercov
supercorp-ai/supercov
Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.
- Official
Security Review
github/awesome-copilot
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching…
Temporal Developer
latitude-dev/latitude-llm
This skill should be used when the user asks to "create a Temporal workflow", "write a Temporal activity", "debug stuck workflow", "fix non-determinism error", "Temporal Python", "Temporal…
K8e Sandbox
xiaods/k8e
Run a goal end to end inside an isolated K8E sandbox pod (gVisor / Kata / Firecracker) instead of on the host: exec bash / Python / Node / TypeScript, install packages, move files in and out, reuse…
Using Message Queues
ancoleman/ai-design-components
Async communication patterns using message brokers and task queues.
Related
Categories
Questions about Temporal Developer
What does Temporal Developer do?
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Temporal Developer is an agent skill from temporalio/skill-temporal-developer, published by the product's own GitHub organization.NET, Ruby, and Rust.
When should I use Temporal Developer?
Temporal Developer fits situations like: the user is building workflows; background job queues with a Temporal SDK; debugging issues like non-determinism errors; stuck workflows.
How do I install Temporal Developer in Claude Code?
Run `npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a claude-code`. Or copy the skill folder (the temporalio/skill-temporal-developer repository) into .claude/skills/temporal-developer in your project. Claude Code loads it when a task matches its description.
How do I install Temporal Developer in Codex?
Run `npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a codex`. Or copy the skill folder (the temporalio/skill-temporal-developer repository) into .agents/skills/temporal-developer in your project. Codex loads it when a task matches its description.
Can I use Temporal Developer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add temporalio/skill-temporal-developer --skill temporal-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/temporal-developer, .gemini/skills/temporal-developer, .github/skills/temporal-developer and .opencode/skills/temporal-developer in your project.
What does Temporal Developer need to run?
SKILL.md names no scripts, command-line tools or credentials: Temporal Developer is instructions for the agent only. Our summary lists: Python 3.
Does Temporal Developer access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Temporal Developer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Temporal Developer use?
Temporal Developer is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Temporal Developer use?
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 210k tokens, read only when the agent opens those files.
What are the alternatives to Temporal Developer?
Skills that share tags, products or a category with Temporal Developer: Dbg (theodo-group/debug-that, 158 stars), Supercov (supercorp-ai/supercov, 148 stars), Security Review (github/awesome-copilot, 40k stars) and Temporal Developer (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Temporal Developer?
temporalio (a GitHub organization, an official publisher) maintains it in temporalio/skill-temporal-developer, which has 230 GitHub stars. The repository was last updated on October 6, 2026.
Source: temporalio/skill-temporal-developer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.