Name: saga-orchestration
Rating: 47.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

saga-orchestration

Patterns for managing distributed transactions and long-running business processes.

Quality

51%

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/saga-orchestration/SKILL.md

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

Quality

Content

53%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 content is strong on actionability with four concrete executable templates, but it is held back by generic boilerplate, the absence of explicit validation checkpoints in the workflow, and a monolithic structure whose one file reference is broken.

Suggestions

Move the four large templates into separate reference files (e.g. references/orchestrator-base.py, references/order-fulfillment-saga.py) and keep SKILL.md as a concise overview that links to them.

Create the referenced resources/implementation-playbook.md or remove the dangling reference on line 23 so navigation is not broken.

Replace the generic 'Instructions' and 'Do not use this skill when' boilerplate with a concrete step-by-step saga workflow that includes explicit validation checkpoints (e.g. verify each step idempotency, confirm compensation success before marking FAILED).

Dimension	Reasoning	Score
Conciseness	The bulk is useful, executable template code, but generic boilerplate sections ('Do not use this skill when' with filler like 'The task is unrelated to saga orchestration', and the vague 'Instructions' block) add tokens without earning their place, matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Four full Python templates (orchestrator base, order fulfillment, choreography, timeouts) provide concrete, mostly copy-paste-ready code, with only minor gaps such as the undefined InsufficientInventoryError and a missing timedelta import, fitting 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The templates encode a clear execution sequence (start -> execute -> handle complete/fail -> compensate) but there are no explicit validation/verification checkpoints or feedback loops, and sagas are destructive/batch-style operations, so per the cap workflow clarity stays at 3.	3 / 5
Progressive Disclosure	The body is a monolithic ~500-line document with all four templates inlined rather than split into separate files, and the single navigational reference (resources/implementation-playbook.md) points to a file that does not exist, matching 'Minimal structure; content that clearly belongs in separate files is inlined; or references are buried'.	2 / 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 identifies a clear domain but lacks concrete actions and any explicit 'when to use' guidance, capping completeness at 3. It also omits the most natural trigger term ('saga'), limiting trigger-term quality.

Suggestions

Add a concrete action list, e.g. 'Coordinates multi-service transactions, implements compensating transactions, and manages long-running workflows'.

Append an explicit 'Use when...' clause with natural triggers such as 'saga', 'distributed transactions', 'compensating transactions', and 'microservices workflows'.

Include the term 'saga' in the description itself so users who say the word trigger the skill directly.

Dimension	Reasoning	Score
Specificity	The description names the domain ('distributed transactions and long-running business processes') but the only action verb is the generic 'managing', with no concrete capabilities enumerated, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3 ('Has a clear what but when is missing or only weakly implied').	3 / 5
Trigger Term Quality	'distributed transactions' and 'long-running business processes' are relevant natural phrases, but the most common trigger term 'saga' is absent from the description, as are 'microservices' and 'compensating transactions', fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The distributed-transactions / long-running-process niche is fairly distinct, with only minor overlap risk against closely related skills like workflow-automation, matching 'Mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (508 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/saga-orchestration/SKILL.md
Commit: 57c135b

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