CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

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

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

Dense, highly actionable code templates give this skill real implementation value with almost no concept over-explanation, but everything is inlined in one large file and the implementer's validation workflow (especially compensation testing) stays implicit. The generic Instructions/Do-not-use boilerplate and a few undefined symbols in the templates are the main trim-and-fix items. Anti-drift check against neighboring anchors confirmed all four placements.

Suggestions

Move the four code templates into separate bundle files (e.g. templates/orchestrator.py, templates/order-fulfillment.py, templates/choreography.py, templates/timeouts.py) and keep SKILL.md as a concise overview that signals when to use each, reducing the main body to selection guidance.

Add an explicit implementation workflow with validation checkpoints, e.g. 1) define steps and their compensations, 2) implement service handlers, 3) verify each compensation reverses its action, 4) inject failure at every step and confirm rollback — turning the "Don't skip compensation testing" advice into a concrete sequence with a feedback loop.

Fix the minor executability gaps: import timedelta and add a timeout_at field to SagaStep in Template 4, and define or footnote InsufficientInventoryError in Template 2; also delete the generic "Instructions" and "Do not use this skill when" boilerplate sections.

DimensionReasoningScore

Conciseness

The body is dominated by dense, non-redundant code templates with no tutorial-style explanation of concepts Claude already knows, and Best Practices are terse ("Make steps idempotent - Safe to retry"). Not 5 because boilerplate sections — "Clarify goals, constraints, and required inputs" / "The task is unrelated to saga orchestration" — are generic filler that earns no tokens; not 3 because the unnecessary prose is a small fraction of an otherwise efficient ~490 lines.

4 / 5

Actionability

Four largely complete Python templates (orchestrator base, order fulfillment, choreography, timeouts) provide near copy-paste-ready guidance covering the common cases. Not 5 because of minor executability gaps: Template 4 uses timedelta and step.timeout_at without importing timedelta or adding the field to SagaStep, InsufficientInventoryError is undefined, and saga_store/event_publisher interfaces are unspecified; not 3 because the code is real executable Python, not pseudocode.

4 / 5

Workflow Clarity

The saga lifecycle sequence is modeled in code (start → execute → handle completion/failure → compensate) and the state table, but implementer-facing checkpoints are absent — "Don't skip compensation testing" is asserted with no verify/test workflow, and sagas involve rollback of distributed transactions, so missing validation steps cap this at 3. Not 4 because validation is implicit only; not 2 because a coherent sequence is clearly present.

3 / 5

Progressive Disclosure

Sections are clearly headed (Core Concepts, Templates, Best Practices, Resources) and there are no nested references, but ~400 lines of code templates are inlined in SKILL.md with no references/ or scripts/ bundle files — content that clearly belongs in separate template files lives inline. Not 4 because for a skill this size the all-inline structure is a real organization gap; not 2 because the section structure is good, not minimal.

3 / 5

Total

14

/

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.

A strong description that explicitly states both the capability and the trigger conditions in domain-precise third-person language with no filler. Minor gains are available from adding synonyms (rollback, orchestration) and slightly more concrete action verbs. Anti-drift check against neighboring anchors confirmed all four placements.

DimensionReasoningScore

Specificity

The description names the domain ("saga patterns for distributed transactions and cross-aggregate workflows") and lists several actions — "Implement saga patterns", "handling compensating transactions", "coordinating multi-step business processes", "managing long-running workflows" — but the verbs remain somewhat abstract, leaving minor gaps versus comprehensive coverage. Not 5 because the actions are gerund-level abstractions rather than fully concrete operations; not 3 because multiple distinct actions beyond the domain name are given.

4 / 5

Completeness

"Implement saga patterns for distributed transactions and cross-aggregate workflows" explicitly answers what, and "Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows" gives explicit when-triggers with concrete phrases. This matches the 5 anchor (both what and when clearly and explicitly answered with concrete trigger phrases); the 4 anchor's "when could be more explicit" does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say — "distributed transactions", "compensating transactions", "multi-step business processes", "long-running workflows" — are all present, giving good keyword coverage. Not 5 because common synonyms and variants such as "rollback", "orchestration", "choreography", or "event-driven" are missing; not 3 because coverage goes well beyond a single domain keyword.

4 / 5

Distinctiveness Conflict Risk

"saga patterns" and "compensating transactions" carve a clear niche with distinct triggers, but "managing long-running workflows" and "multi-step business processes" are broad enough to overlap with generic workflow-orchestration skills. Not 5 due to that minor overlap risk; not 3 because the core triggers are domain-specific rather than merely "somewhat specific".

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

Path

skills/saga-orchestration/SKILL.md

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.