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:wshobson/agents --skill workflow-orchestration-patternsOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 92%
↓ 0.99xAgent success when using this skill
Validation for skill structure
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 uses third person voice correctly, provides specific technical capabilities, includes natural trigger terms that developers would use, and has an explicit 'Use when' clause with clear scenarios. The Temporal-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'workflow vs activity separation, saga patterns, state management, and determinism constraints' - these are concrete, actionable concepts within the Temporal domain. | 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Temporal', 'distributed systems', 'workflows', 'long-running processes', 'distributed transactions', 'microservice orchestration', 'saga patterns' - good coverage of terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Temporal' as a specific technology, plus domain-specific terms like 'saga patterns', 'determinism constraints', and 'durable workflows' that clearly distinguish it from generic workflow or orchestration skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
63%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 (relying on pseudocode and prose descriptions) 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 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). The design decision framework provides clear decision points, and error handling/retry strategies are well-documented with validation considerations. | 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 into separate files. The 'Additional Resources' section references external docs but doesn't link to internal detailed guides for each pattern. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.