workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill workflow-orchestration-patterns86
Quality
81%
Does it follow best practices?
Impact
92%
0.98xAverage score across 3 eval scenarios
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It names the specific technology (Temporal), lists concrete technical concepts it covers, and provides explicit 'Use when' guidance with natural trigger terms. The description is concise yet comprehensive, making it easy for Claude to select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'workflow vs activity separation, saga patterns, state management, and determinism constraints' - these are concrete, technical capabilities that clearly describe what the skill covers. | 3 / 3 |
Completeness | Clearly answers both what ('Design durable workflows with Temporal... Covers workflow vs activity separation, saga patterns, state management, and determinism constraints') AND when ('Use when building long-running processes, distributed transactions, or microservice orchestration') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Temporal', 'distributed systems', 'workflows', 'long-running processes', 'distributed transactions', 'microservice orchestration' - good coverage of terms developers would naturally use when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - 'Temporal' is a specific technology, and the combination of 'saga patterns', 'determinism constraints', and 'durable workflows' creates a unique fingerprint unlikely to conflict with generic workflow or distributed systems skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive conceptual coverage of Temporal workflow patterns with good structural organization and clear workflow sequencing. However, it lacks executable code examples (showing patterns in prose rather than implementation) and could be more concise by removing explanations of concepts Claude already understands. The content would benefit from actual Python/TypeScript code snippets demonstrating the patterns.
Suggestions
Add complete, executable code examples for each pattern (Saga, Entity, Fan-Out) instead of prose descriptions - show actual Temporal SDK usage
Remove explanatory content Claude already knows (e.g., what distributed transactions are, basic definitions) and focus on Temporal-specific implementation details
Split detailed pattern implementations into separate reference files (e.g., SAGA_PATTERN.md, ENTITY_WORKFLOWS.md) and keep SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some explanatory text that Claude would already know (e.g., explaining what sagas are, basic definitions of workflows vs activities). Some sections like 'When NOT to Use' and 'Ideal Use Cases' could be more condensed. | 2 / 3 |
Actionability | Provides conceptual guidance and patterns but lacks executable code examples. The 'Example: Payment Workflow' is described in prose rather than actual code. Patterns are described abstractly (e.g., 'Use workflow.now()') without showing complete, copy-paste ready implementations. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced, especially the Saga pattern with explicit ordering (register compensation BEFORE executing, run in reverse LIFO order). The decision framework ('Does it touch external systems? → Activity') provides clear checkpoints. Error handling and retry strategies are well-documented. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document that could benefit from splitting detailed patterns (Saga, Entity, Fan-Out) into separate reference files. The 'Additional Resources' section provides external links but no internal file references for deeper content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.