CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/backend-development/skills/workflow-orchestration-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a high-level conceptual guide rather than an actionable skill for Claude. It lacks any executable code examples despite covering a code-heavy domain (Temporal SDK), provides no step-by-step workflows to follow, and relies heavily on a referenced details file that doesn't exist in the bundle. The content would benefit greatly from concrete code examples showing workflow/activity separation and saga patterns, which are the core promises of the skill description.

Suggestions

Add concrete, executable code examples showing workflow definition, activity implementation, and saga pattern compensation—at minimum a complete workflow+activity pair in Python or TypeScript using the Temporal SDK.

Create a clear step-by-step workflow for building a Temporal workflow (e.g., 1. Define workflow interface, 2. Implement activities, 3. Configure retry policies, 4. Test with time-skipping) with validation checkpoints.

Either include the referenced 'references/details.md' bundle file or inline the essential patterns and worked examples into the SKILL.md itself.

Remove the 'When NOT to Use' and 'Additional Resources' sections to save tokens, and replace with actionable content like code templates and concrete configuration examples.

DimensionReasoningScore

Conciseness

The skill contains some unnecessary padding—lists of 'when NOT to use' cases and 'additional resources' with external URLs add limited value for Claude. The best practices and pitfalls sections are reasonably efficient but could be tightened. Some items like 'State preservation is automatic' under Key Principles explain things Claude already knows about Temporal.

2 / 3

Actionability

The skill provides no executable code, no concrete commands, no copy-paste examples. It reads as a conceptual overview with bullet-point advice ('keep workflows focused', 'idempotent operations') rather than actionable instructions. There are no code snippets showing workflow/activity separation, saga implementation, or any Temporal SDK usage.

1 / 3

Workflow Clarity

Despite being a skill about workflow orchestration, there are no sequenced multi-step processes for Claude to follow. No validation checkpoints, no feedback loops, no clear 'do X then Y then Z' instructions. The content is entirely descriptive best practices and lists rather than a workflow Claude can execute.

1 / 3

Progressive Disclosure

The skill references 'references/details.md' for detailed patterns and worked examples, which is a reasonable progressive disclosure structure. However, no bundle files are provided, so the referenced file doesn't exist, and the main SKILL.md itself lacks the substantive overview content that should precede the reference—it jumps from use cases directly to best practices with the detail file doing all the heavy lifting.

2 / 3

Total

6

/

12

Passed

Description

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 strong skill description that clearly identifies the technology (Temporal), lists specific capabilities (saga patterns, determinism constraints, workflow/activity separation), and provides explicit trigger guidance for when to use it. The description is concise, uses third-person voice, and covers natural terms developers would use when seeking help with Temporal-based distributed systems.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: workflow vs activity separation, saga patterns, state management, determinism constraints, and durable workflows with Temporal.

3 / 3

Completeness

Clearly answers both 'what' (design durable workflows with Temporal, covering workflow vs activity separation, saga patterns, state management, determinism constraints) and 'when' (explicit 'Use when building long-running processes, distributed transactions, or microservice orchestration').

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'Temporal', 'distributed systems', 'saga patterns', 'long-running processes', 'distributed transactions', 'microservice orchestration', 'workflow', 'activity', 'determinism'. These cover the key terms a developer working with Temporal would use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific mention of 'Temporal' as the framework, combined with domain-specific concepts like saga patterns and determinism constraints. Unlikely to conflict with generic workflow or microservice skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.