Use when building durable distributed systems with Temporal Go SDK. Covers deterministic workflow rules, mTLS worker configs, and advanced patterns.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/11/2026
What it changes
Passed 16 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill73%
Checks it passed that the model alone missed
Uses workflow.Now to get the current time.
1 fixed15 passed either way6 still failing0 broke
Pass-rate lift
+5 pp
Tokens
+91%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/11/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
I need to record the exact start time of my Go Temporal workflow and pass it as a parameter to an activity. Provide the workflow snippet.
What was checked, without and with the skill
Checked
Without skill
With skill
Uses workflow.Now to get the current time.
Missed
Passed
Does not use time.Now.
Passed
Passed
case-16 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md208 linessingle file
Temporal Go SDK (temporal-golang-pro)
Overview
Expert-level guide for building resilient, scalable, and deterministic distributed systems using the Temporal Go SDK. This skill transforms vague orchestration requirements into production-grade Go implementations, focusing on durable execution, strict determinism, and enterprise-scale worker configuration.
When to Use This Skill
Designing Distributed Systems: When building microservices that require durable state and reliable orchestration.
Implementing Complex Workflows: Using the Go SDK to handle long-running processes (days/months) or complex Saga patterns.
Optimizing Performance: When workers need fine-tuned concurrency, mTLS security, or custom interceptors.
Verify Determinism: Before suggesting workflow code, verify against these 5 Rules:
No native Go concurrency (goroutines).
No native time (time.Now, time.Sleep).
No non-deterministic map iteration (must sort keys).
No direct external I/O or network calls.
No non-deterministic random numbers.
Implement Incrementally: Start with shared Protobuf/Data classes, then Activities, then Workflows, and finally Workers.
Leverage Resources: If the implementation requires advanced patterns (Sagas, Interceptors, Replay Testing), explicitly refer to the implementation playbook and testing strategies.