CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/saga-orchestration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 highly actionable with comprehensive code templates, but it is held back by generic filler, missing validation checkpoints for destructive compensations, and a monolithic structure that should offload templates into reference files.

Suggestions

Remove the generic 'Instructions' and tautological 'Do not use this skill when' sections; replace with concise, saga-specific guidance that earns its tokens.

Add an explicit validation/verification feedback loop (e.g., verify each step result before advancing, and confirm compensation succeeded before marking the saga FAILED) to lift workflow clarity above the destructive/batch cap of 3.

Move the four large code templates into separate files under references/ (e.g., references/orchestrator_base.py, references/order_fulfillment.py) and link to them from SKILL.md so the main file stays a lean overview.

DimensionReasoningScore

Conciseness

The body avoids re-explaining known concepts and is mostly code, but the generic 'Instructions' and tautological 'Do not use this skill when' sections are padding that could be trimmed.

3 / 5

Actionability

Four largely executable Python templates cover orchestration, choreography, order fulfillment, and timeouts, with minor gaps such as a missing 'timedelta' import and undefined exception/interface types.

4 / 5

Workflow Clarity

The saga state machine and execution sequence are clear, but sagas involve destructive compensating rollbacks with no explicit validation/verification feedback loop, capping this dimension at 3.

3 / 5

Progressive Disclosure

A ~490-line monolithic file inlines four large code templates that belong in separate reference files; section headers provide some structure, but no bundle files exist and content is not split out.

3 / 5

Total

13

/

20

Passed

Description

83%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 is strong: it concisely states the capability and provides an explicit, multi-trigger 'Use when' clause. It is mostly distinct and actionable, with only minor overlap risk and modest keyword breadth.

DimensionReasoningScore

Specificity

Names the domain ('saga patterns', 'distributed transactions') and lists several concrete actions (coordinating multi-step processes, handling compensating transactions, managing long-running workflows), with only minor coverage gaps.

4 / 5

Completeness

Explicitly states both what the skill does ('Implement saga patterns...') and when to use it via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer-facing terms like 'saga patterns', 'compensating transactions', and 'long-running workflows', but lacks synonyms or broader keyword variants that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

'saga' and 'compensating transactions' carve a distinct niche, but 'long-running workflows' and 'multi-step business processes' are broad enough to overlap with general workflow tooling.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.