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.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

46%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 well-structured conceptual reference for Temporal orchestration patterns with clear decision rules, but it is padded with generic filler sections, restates concepts Claude already knows, and lacks executable code or validation feedback loops. Tightening the filler and adding concrete SDK examples would lift it materially.

Suggestions

Remove the generic 'Use this skill when', 'Do not use this skill when', and 'Instructions' boilerplate sections—these add no skill-specific signal and waste context.

Replace pseudocode rules and prose pattern descriptions with executable Temporal SDK snippets (e.g. a saga showing workflow.get_version, activity registration, and compensation invocation in Python/Go/TypeScript).

Add an explicit validation/feedback loop for the design process—e.g. a checklist to verify determinism constraints and idempotency before considering a workflow design complete.

Dimension	Reasoning	Score
Conciseness	Generic templated filler ('Working on workflow orchestration patterns tasks or workflows', 'The task is unrelated...', 'Clarify goals... Apply relevant best practices and validate outcomes') plus conceptual restatement of things Claude already knows (idempotency, determinism basics) make it noticeably padded despite the bulleted core.	2 / 5
Actionability	It gives concrete decision rules and sequenced pattern steps (e.g. 'Register compensation BEFORE executing step', 'Run compensations in reverse order'), but offers only pseudocode rules and no executable Temporal SDK code, leaving key implementation details unspecified.	3 / 5
Workflow Clarity	Individual patterns (saga, fan-out) carry clear step sequences, but there is no end-to-end workflow with explicit validation checkpoints or a validate→fix→retry feedback loop for the design process.	3 / 5
Progressive Disclosure	A single ~330-line file is well-organized with clear headers (Use Cases, Patterns, State Management, Resilience, Best Practices) and external doc citations; no nested references, though the length is enough that splitting detailed patterns into bundled references could help.	4 / 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, well-formed description: third-person voice, explicit what-and-when, and a specific named tool that distinguishes it from generic orchestration skills. Minor gaps in action inventory and synonym coverage keep specificity and trigger quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names the domain (Temporal) and lists several concrete capabilities—'workflow vs activity separation, saga patterns, state management, and determinism constraints'—but presents them as coverage topics rather than a comprehensive action inventory.	4 / 5
Completeness	It explicitly answers both 'what' ('Design durable workflows with Temporal... Covers...') and 'when' with concrete trigger phrases in the 'Use when' clause, matching the top anchor.	5 / 5
Trigger Term Quality	'Use when building long-running processes, distributed transactions, or microservice orchestration' supplies natural phrases users would say, with good coverage; a few common synonyms (scheduled jobs, event-driven, sagas) are absent.	4 / 5
Distinctiveness Conflict Risk	Naming the specific tool Temporal plus the niche of durable workflow orchestration gives it a clear, distinct trigger surface with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/workflow-orchestration-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.