Skip to content
Back to skills

Saga Orchestration

ASecurity

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

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentstesting

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add huytran1120/vietnam-agentic-skills --skill saga-orchestration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Saga Orchestration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Saga Orchestration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/huytran1120-saga-orchestration/badge)](https://www.skillsdirectory.com/skills/huytran1120-saga-orchestration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: saga-orchestration
description: "Patterns for managing distributed transactions and long-running business processes."
risk: critical
source: community
date_added: "2026-02-27"
---

# Saga Orchestration

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

## Detailed Guide

Read [the detailed guide](references/detailed-guide.md) 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.

## Example

After inventory reservation succeeds, a payment timeout is an unknown outcome.
Query the provider using the original idempotency key before charging again or
releasing inventory; record the resolution and retry compensation durably.

Files in this skill

  • SKILL.md1.6 KB
  • references/detailed-guide.md18.4 KB
  • resources/implementation-playbook.md911 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.