Name: workflow-orchestration-patterns
Rating: 46.400000000000006 (1 reviews)
Author: administrakt0r

workflow-orchestration-patterns

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

Quality

49%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/workflow-orchestration-patterns/SKILL.md

The canonical home for this skill is workflow-orchestration-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The body is a well-organized Temporal patterns reference with genuinely useful design rules, but it behaves as an inlined reference document rather than an overview, lacks executable code, and references a non-existent playbook file.

Suggestions

Move the detailed pattern catalog and resource lists into separate reference files and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links to files that actually exist.

Add at least one executable Temporal SDK example (a workflow + activity definition) so guidance is copy-paste ready rather than pseudocode.

Replace the generic 'Instructions' boilerplate with a concrete, sequenced workflow that includes validation checkpoints (e.g. verify determinism constraints, confirm activity idempotency before deployment).

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured with domain-specific guidance, but the ~330-line body inlines a full reference and repeats earlier points in the closing 'Key Principles' list, so it could be tightened.	3 / 5
Actionability	Provides concrete design rules (prohibited/allowed APIs, retry config fields, idempotency strategies) but delivers patterns as pseudocode and prose with no executable Temporal SDK code, leaving guidance incomplete.	3 / 5
Workflow Clarity	The 'Instructions' section offers a rough sequence but it is generic boilerplate ('Apply relevant best practices and validate outcomes') with no real validation checkpoints, and the body is organized by pattern rather than as a sequenced workflow.	3 / 5
Progressive Disclosure	Good section structure exists, but the bulk of the reference is inlined in SKILL.md and its one external reference ('resources/implementation-playbook.md') points to a path that does not exist, so references are not clearly signaled or real.	3 / 5
	Total	12 / 20 Passed

Description

48%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.

The description clearly identifies the Temporal workflow-orchestration niche but reads as a topic catalog rather than a statement of concrete capabilities, and it omits any explicit 'Use when' trigger guidance.

Suggestions

Replace topic-area phrasing ('covering design decisions, resilience patterns') with concrete capabilities (e.g. 'design workflows vs activities, implement saga compensation, configure retry policies and idempotent activities').

Add an explicit trigger clause, e.g. 'Use when building durable workflows or distributed transactions with Temporal'.

Include natural synonyms users would say ('durable execution', 'saga pattern', 'workflow engine') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('workflow orchestration architecture with Temporal') but the 'actions' are topic categories ('covering fundamental design decisions, resilience patterns, and best practices') rather than concrete capabilities, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Gives a clear 'what' but has no 'Use when...' or equivalent explicit trigger guidance; per the rubric, a missing 'when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'workflow orchestration' and 'Temporal' that users would say, but misses common variations/synonyms (e.g. 'durable execution', 'saga', 'workflow engine', 'microservices orchestration'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tool 'Temporal' carves a distinct niche with minimal conflict risk, though 'reliable distributed systems' and 'best practices' broaden it slightly into overlap with general distributed-systems skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/workflow-orchestration-patterns/SKILL.md
Commit: 900c504

Reviewed: 2 hours 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.