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.

78

0.98x
Quality

68%

Does it follow best practices?

Impact

92%

0.98x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/workflow-orchestration-patterns/SKILL.md

The canonical home for this skill is workflow-orchestration-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-5

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

A thorough conceptual reference for Temporal patterns that is well-structured but stays at the abstract/pseudocode level, lacking executable code, validation feedback loops, and any progressive disclosure into bundle files. It reads more like documentation than an actionable skill.

Suggestions

Add at least one executable Temporal SDK example (a real workflow definition plus an activity registration) so guidance is copy-paste ready instead of pseudocode.

Insert explicit validation/verification checkpoints and fix-and-retry loops into the saga and other destructive-operation patterns (e.g., verify compensation succeeded before proceeding).

Split the monolithic 316-line body into one-level-deep bundle files (e.g., patterns.md, best-practices.md) referenced clearly from a concise overview in SKILL.md, and trim re-explanations of concepts Claude already knows.

DimensionReasoningScore

Conciseness

The 316-line body is well-organized with bullets, but re-explains concepts Claude already knows (what workflows vs activities are, why idempotency matters, determinism basics) that could be tightened.

3 / 5

Actionability

Provides pseudocode patterns and names concrete APIs/fields (workflow.get_version, workflow.now, backoff coefficient, max attempts), but contains zero executable Temporal SDK code — all examples are abstract pseudocode rather than copy-paste ready.

3 / 5

Workflow Clarity

Patterns like the saga are sequenced ('Register compensation BEFORE executing → Execute → On failure run compensations LIFO'), but there are no validation checkpoints or fix-and-retry feedback loops; the destructive/batch cap at 3 applies.

3 / 5

Progressive Disclosure

Headers and subsections are well-organized, but the skill is a 316-line monolith with no bundle files and no one-level-deep references to split out the patterns, best-practices, or API material.

3 / 5

Total

12

/

20

Passed

Description

87%Weight 40%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.

A strong, third-person description that clearly states both capability and trigger conditions with a well-defined Temporal niche. Minor improvement is possible by converting 'Covers' topics into more concrete action verbs and adding a few more natural synonyms.

DimensionReasoningScore

Specificity

Names the Temporal domain plus several concrete capability areas ('workflow vs activity separation, saga patterns, state management, and determinism constraints'), but the action verbs are limited to 'Design' and 'Covers' rather than many distinct concrete actions.

4 / 5

Completeness

Explicitly answers both what ('Design durable workflows with Temporal... Covers workflow vs activity separation, saga patterns...') and when ('Use when building long-running processes, distributed transactions, or microservice orchestration') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('long-running processes, distributed transactions, or microservice orchestration') plus 'durable workflows' and 'saga patterns', but misses common synonyms like 'workflow engine' or 'task orchestration'.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to Temporal workflow orchestration with distinct triggers ('durable workflows with Temporal', 'microservice orchestration'), giving it a clear niche with minimal overlap risk.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dicklesworthstone/pi_agent_rust
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.