FRAMEWORK DEVELOPMENT / Temporal Technologies
Temporal Developer
Temporal SDK guidance across seven languages, centred on replay determinism, versioning and wrapping LLM calls in activities.
“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".”
01 / THE REASONING
Why this made the selection.
- It explains history replay and why a non-determinism error blocks a workflow, then routes to core and language-specific determinism, versioning and pitfalls references.
- If the skill itself is unclear, the agent drafts a GitHub issue body and asks the user to file it; the file says not to file it autonomously.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- SKILL.md (out of scope, core architecture, history replay, reference routing, job queues, feedback)
- references/core/ai-patterns.md (overview and core patterns)
- README.md (installation, supported SDK languages)
- LICENSE MIT, copyright 2026 Temporal Technologies Inc.
Our findings
- Job-queue requests are answered with Standalone Activities, and Temporal Task Queues are kept distinct from job queues, per the file.
- references/core/ai-patterns.md puts LLM calls and non-deterministic tools in activities.
Not established by this review
- The installer was not run, and the skill was not executed against a project or service. No workflow was run.
- The language-specific references and the remaining core references were not opened.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add temporalio/skill-temporal-developer Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
- The README lists this as step 1 of the npx skills install, followed by the installer prompts. Plugin packages for Claude Code, Cursor and Codex live in separate repositories that were not reviewed.
- The command does not pin revision 3041178b597dddb1b54f49e5e73fbae644fba283. Compare the installed SKILL.md and references with that revision.
Before you start
- Node.js and npm for the documented Skills installer
- A Temporal SDK, and the Temporal CLI only for local dev-server tasks
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Skill definition ↗Checked
https://github.com/temporalio/skill-temporal-developer/blob/3041178b597dddb1b54f49e5e73fbae644fba283/SKILL.md
Supports: summary, upstreamDescription, whySelected, limitations, access, review
https://github.com/temporalio/skill-temporal-developer/blob/3041178b597dddb1b54f49e5e73fbae644fba283/references/core/ai-patterns.md
Supports: review, bestFor
https://github.com/temporalio/skill-temporal-developer/blob/3041178b597dddb1b54f49e5e73fbae644fba283/README.md
Supports: install, compatibility
- Repository licence ↗Checked
https://github.com/temporalio/skill-temporal-developer/blob/3041178b597dddb1b54f49e5e73fbae644fba283/LICENSE
Supports: license