CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-orchestration-patterns

Master workflow orchestration architecture with Temporal, covering fundamental design decisions, resilience patterns, and best practices for building reliable distributed systems.

36

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow-orchestration-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%Scale 1-5

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

This skill reads more like a Temporal documentation summary than an actionable skill for Claude. It extensively explains concepts Claude already understands (distributed systems patterns, idempotency, retry logic) without providing any executable code examples in any Temporal SDK. The referenced implementation playbook is missing from the bundle, leaving the skill without concrete implementation guidance.

Suggestions

Add concrete, executable code examples using a specific Temporal SDK (e.g., Python or TypeScript) for at least the Saga pattern and Entity workflow patterns, replacing the abstract descriptions.

Remove or drastically condense sections explaining concepts Claude already knows (what idempotency is, what retry policies are, when to use workflows vs direct API calls) and focus on Temporal-specific implementation details.

Create and include the referenced 'resources/implementation-playbook.md' with detailed code examples, or remove the reference if the file doesn't exist.

Add explicit validation steps for workflow implementations, such as how to test determinism, verify idempotency, and validate compensation logic using Temporal's testing framework.

DimensionReasoningScore

Conciseness

The skill is noticeably verbose, explaining many concepts Claude already knows well (what workflows vs activities are, what Saga pattern is, what idempotency means, what retry policies are). The 'When to Use' and 'When NOT to Use' sections, determinism constraints, and best practices are largely general knowledge for Claude. Much of this reads like a tutorial rather than a concise reference.

2 / 5

Actionability

Despite covering many patterns, the skill provides no executable code examples—only abstract descriptions and pseudocode-like patterns (e.g., 'Register compensation BEFORE executing'). There are no concrete Temporal SDK code snippets, no specific API calls, no copy-paste ready implementations. The referenced 'resources/implementation-playbook.md' is not provided in the bundle.

2 / 5

Workflow Clarity

The skill describes several workflow patterns with reasonable sequencing (Saga steps, fan-out/fan-in), but lacks explicit validation checkpoints or feedback loops. For a skill about orchestration that involves distributed transactions and compensating actions, there are no verification steps or error recovery procedures beyond abstract mentions of 'handle partial failures gracefully.'

3 / 5

Progressive Disclosure

The skill references 'resources/implementation-playbook.md' but this file is not provided in the bundle, making the reference a dead link. The content is a monolithic wall of text (~250 lines) that would benefit from splitting into separate files (patterns, best practices, anti-patterns). External documentation links are provided but are URLs rather than bundle files.

2 / 5

Total

9

/

20

Passed

Description

36%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the technology domain (Temporal) but relies heavily on abstract, buzzword-heavy language ('master workflow orchestration architecture', 'fundamental design decisions', 'best practices') without specifying concrete actions or when to use the skill. It lacks a 'Use when...' clause and misses many natural trigger terms that users working with Temporal would actually say.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases like 'Use when the user asks about Temporal workflows, activity retries, saga patterns, worker configuration, or workflow orchestration with Temporal.'

Replace abstract terms like 'design decisions' and 'best practices' with specific capabilities such as 'design retry and timeout policies, implement saga patterns, configure workers, handle signals and queries, structure workflow and activity code.'

Include natural synonyms and related terms users might mention, such as 'Temporal SDK', 'durable execution', 'workflow replay', 'activity heartbeat', or specific language SDKs like 'Temporal Go SDK' or 'Temporal TypeScript SDK'.

DimensionReasoningScore

Specificity

Names the domain (Temporal workflow orchestration) but actions are vague and generic — 'design decisions', 'resilience patterns', and 'best practices' are abstract categories rather than concrete actions like 'design retry policies' or 'implement saga patterns'.

2 / 5

Completeness

Has a vague 'what' (covers design decisions, resilience patterns, best practices) but completely lacks any 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per the rubric, and the 'what' is itself quite vague, bringing it to 2.

2 / 5

Trigger Term Quality

Includes 'Temporal' and 'workflow orchestration' which are relevant keywords, plus 'distributed systems' and 'resilience patterns'. However, it misses natural user phrases like 'Temporal workflow', 'activity', 'worker', 'saga', 'retry policy', 'signal', 'query', or specific Temporal SDK terms users would mention.

3 / 5

Distinctiveness Conflict Risk

Mentioning 'Temporal' specifically helps distinguish it from generic distributed systems skills, but the broad terms 'resilience patterns', 'best practices', and 'distributed systems' could overlap with general architecture or microservices skills.

3 / 5

Total

10

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.