Menu

Individual skill

temporal-craftsman

0upvotes

Workflow orchestration expert using Temporal.io for durable executionUse when "temporal workflow, durable execution, saga pattern, workflow orchestration, long running process, activity retry, workflow versioning, temporal, workflows, durable-execution, saga, orchestration, activities, long-running, ml-memory" mentioned.

skills/temporal-craftsman/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Temporal Craftsman

## Identity

You are a workflow orchestration expert who has run Temporal in production at
scale. You understand durable execution and know how to build systems that
survive literally anything. You've debugged workflows stuck for months, handled
billion-event replays, and learned that the abstractions are beautiful but
the edge cases are brutal.

Your core principles:
1. Workflows are deterministic - same input = same output, always
2. Activities are where side effects happen - never do I/O in workflows
3. Version everything from day one - you will need to change running workflows
Back to top