saga-orchestration

Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.

Quality

77%

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

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable, built around four complete, executable saga templates, and is clearly sectioned. Its weaknesses are token efficiency (generic boilerplate plus heavy inline code) and the absence of explicit validation checkpoints and reference-file separation for the large templates.

Suggestions

Remove the generic 'Instructions' and 'Do not use this skill when' boilerplate, or replace it with saga-specific guidance, to improve conciseness.

Add an explicit validation checkpoint to the workflow (e.g., 'verify saga state and confirm all steps completed before marking COMPLETED; re-run compensation if a compensating action fails').

Move the longer templates (choreography, timeouts) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The four templates are concrete and mostly earn their tokens, but the generic 'Instructions' ('Apply relevant best practices and validate outcomes') and 'Do not use this skill when' sections are filler, and the large inline templates could be tightened — matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides four full, executable Python class implementations (orchestrator base, order fulfillment saga, choreography saga, timeout orchestrator) that are copy-paste ready with concrete usage examples, matching the score-3 anchor.	3 / 3
Workflow Clarity	The state table and orchestrator code give a clear sequence with a compensation feedback loop, but there are no explicit validation/verification checkpoints for these distributed-transaction workflows, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned with headers, but ~350 lines of template code that could live in separate reference files are inlined, and no bundle files exist — matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 is strong: it explicitly covers both what the skill does and when to use it, with distinct, natural trigger terms targeting a clear niche. Its only weakness is specificity, since it leads with a single action verb rather than enumerating several concrete capabilities.

Suggestions

Lead with several concrete actions (e.g., 'Define, execute, and compensate multi-step sagas; coordinate services via orchestration or choreography') to lift specificity to a 3.

Add common user variations/synonyms (e.g., 'distributed transactions', 'rollback workflows', 'outbox pattern') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('saga patterns for distributed transactions and cross-aggregate workflows') and the action 'Implement', but lists only one concrete action verb rather than multiple specific capabilities as the score-3 anchor requires.	2 / 3
Completeness	It states what the skill does ('Implement saga patterns...') and gives an explicit 'Use when...' trigger clause, clearly answering both what and when as the score-3 anchor requires.	3 / 3
Trigger Term Quality	It covers natural terms a developer would say — 'saga patterns', 'distributed transactions', 'compensating transactions', 'long-running workflows' — matching the score-3 expectation of good coverage of terms users actually voice.	3 / 3
Distinctiveness Conflict Risk	Saga orchestration is a narrow, well-defined niche with distinct triggers (compensating transactions, cross-aggregate workflows) unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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/saga-orchestration/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.