Description
saga-orchestration is an agent skill from the wshobson/agents collection for implementing saga patterns, which coordinate distributed transactions and long-running business processes across several services without using two-phase commit. A saga is a sequence of steps, each handled by a service, where every step that succeeds has a compensating action that can undo it if a later step fails. The skill is organized around inputs and outputs. The inputs are the service boundaries and which service owns which step, the transaction requirements that say which steps must be atomic and which can be eventually consistent, the failure modes of each step, including whether a failure is transient or permanent and what the retry policy should be, the time limits each step must meet, and the messaging infrastructure already in place, such as Kafka, RabbitMQ or SQS. The outputs are a saga definition with ordered steps and their action and compensation commands, an orchestrator or choreography implementation matching the chosen style, compensation logic for each participant that is idempotent so it can be safely repeated, per-step timeouts, and monitoring for the state machine, including detection of sagas that stop partway and recovery of messages from a dead-letter queue. It applies when implementing distributed transactions across services and cross-aggregate workflows. The skill is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 10.5K installs and passing results from three security audits at the time of the scan.…
Highlights
- Saga definitions with compensating actions
- Orchestration or choreography implementations
- Idempotent compensation logic
- Per-step timeouts and retry policies
- Monitoring for stuck sagas and dead-letter recovery
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate saga-orchestration.
People also visit
spring-boot-engineer
Generates Spring Boot 3.x configurations, creates REST controllers
saga-orchestration FAQ
What is a saga?
A sequence of steps across services where each completed step has a compensating action to undo it if a later step fails.
Does it use two-phase commit?
No. The skill is built on saga patterns, which avoid two-phase commit across services.
What inputs does it need?
Service ownership of each step, which steps must be atomic, failure modes and retry policy, time limits, and the messaging system in use.
What does it produce?
A saga definition, an orchestrator or choreography implementation, compensation logic, per-step timeouts and monitoring setup.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill saga-orchestration.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best saga-orchestration alternatives?
Popular alternatives to saga-orchestration include gtm-positioning-strategy, java-architect and spring-boot-engineer. See all saga-orchestration alternatives