Skills saga-orchestration
🧭

saga-orchestration

Safe 🌐 Network access⚙️ External commands

Design saga workflows for distributed services

Distributed workflows fail when steps do not coordinate or roll back cleanly. This skill provides clear saga patterns and templates to orchestrate steps and compensations for reliable multi-service transactions.

Supports: Claude Codex Code(CC)
📊 71 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "saga-orchestration". Design an order fulfillment saga with compensations and timeouts.

Expected outcome:

  • Steps: reserve inventory, process payment, create shipment, send confirmation.
  • Compensations: release inventory, refund payment, cancel shipment.
  • Timeout policy: fail step after 5 minutes and start compensation.
  • Events: SagaStepCompleted, SagaStepFailed, SagaCompensationCompleted.

Using "saga-orchestration". Compare orchestration and choreography for payment processing.

Expected outcome:

  • Orchestration: central orchestrator sends commands, receives responses.
  • Choreography: services emit events, others subscribe and react.
  • Orchestration benefits: explicit flow, easier debugging, clear ownership.
  • Choreography benefits: loose coupling, no single point of failure.

Using "saga-orchestration". How do I handle a saga step that never completes?

Expected outcome:

  • Implement per-step timeouts in the orchestrator.
  • On timeout, mark step as failed and trigger compensation.
  • Use scheduled tasks to check step status periodically.
  • Log timeout events for monitoring and alerting.

Security Audit

Safe
v4 • 1/17/2026

Pure documentation skill containing code templates for saga pattern implementation. Contains no executable code, filesystem access, network calls, or command execution. All static findings are false positives triggered by documentation text containing technical terminology that scanners incorrectly flag as cryptographic terms, C2 indicators, or shell commands.

2
Files scanned
659
Lines analyzed
2
findings
4
Total audits

Risk Factors

🌐 Network access (3)
skill-report.json:6 SKILL.md:481 SKILL.md:482
⚙️ External commands (9)
SKILL.md:23-34 SKILL.md:34-50 SKILL.md:50-237 SKILL.md:237-241 SKILL.md:241-326 SKILL.md:326-330 SKILL.md:330-416 SKILL.md:416-420 SKILL.md:420-462
Audited by: claude View Audit History →

Quality Score

38
Architecture
100
Maintainability
85
Content
30
Community
100
Security
91
Spec Compliance

What You Can Build

Order fulfillment flow

Design a multi service order workflow with compensation steps and failure handling.

Long running approvals

Model approval workflows with timeouts and rollback behavior.

Saga pattern review

Align teams on orchestration versus choreography tradeoffs.

Try These Prompts

Basic saga design 
Design a saga orchestration for checkout with inventory, payment, and shipping steps. Include compensations and state transitions.
Add timeouts 
Extend a saga orchestrator with per step timeouts and failure handling. Describe how timeouts trigger compensation.
Choreography option 
Provide a choreography based saga for order processing and list event names and handlers.
Advanced failure plan 
Draft a saga plan for a multi stage onboarding flow with retries, compensations, and audit logging guidance.

Best Practices

  • Make steps idempotent for safe retries
  • Design compensations for every irreversible action
  • Use correlation IDs for cross service tracing

Avoid

  • Assume steps complete instantly
  • Skip compensation testing
  • Tightly couple services with direct calls

Frequently Asked Questions

Is this compatible with Claude, Codex, and Claude Code?
Yes. The guidance is platform neutral and works with any assistant that can follow design templates.
What are the limits of this skill?
It provides patterns and templates, not runnable services, storage, or messaging implementations.
How do I integrate with my message bus?
Map the publish and subscribe calls to your bus API and persist saga state in your storage layer.
Does this skill access my data or secrets?
No. It contains static documentation and example templates only.
What should I check if steps never complete?
Verify event delivery, saga state persistence, and timeout scheduling.
How does this compare to choreography only?
Orchestration centralizes control, while choreography spreads logic across services and relies on events.

Developer Details

Author

wshobson

License

MIT

Repository

https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/saga-orchestration

Ref

main

File structure

📄 SKILL.md