Saga Orchestration

This handles distributed transaction patterns using the saga pattern, giving you both choreography and orchestration approaches. You get a Python base orchestrator with state management, step execution, and automatic compensating transactions when things fail. It's built for multi-service workflows like order fulfillment where you need to coordinate across payment, inventory, and shipping services, then roll everything back cleanly if one step fails. The implementation includes saga state tracking, event publishing, and compensation handlers. It's genuinely useful if you're building microservices that need transactional consistency without distributed locks, though you'll need to wire up your own persistence and event bus.

skills.sh installs: 190
GitHub stars: 39.4K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill saga-orchestration --agent claude-code

Installs into .claude/skills of the current project.

Files

Saga Orchestration

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

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

Do not use this skill when

The task is unrelated to saga orchestration
You need a different domain or tool outside this scope

Use this skill when

Coordinating multi-service transactions
Implementing compensating transactions
Managing long-running business workflows
Handling failures in distributed systems
Building order fulfillment processes
Implementing approval workflows

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.