starlark-saga-generation

Generate type-safe Starlark saga scripts aligned with Meridian's transaction orchestration architecture.

10|2|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/meridianhub/meridian --skill starlark-saga-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starlark-saga-generation
Source: https://github.com/meridianhub/meridian/tree/main/.claude/skills/starlark-saga
Command: npx skills add https://github.com/meridianhub/meridian --skill starlark-saga-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meridian teams require a reliable, type-safe way to generate and scaffold Starlark saga scripts that orchestrate distributed transactions with consistent style and minimal manual coding.

Core Features & Use Cases

  • Generate type-safe Starlark saga scripts aligned with Meridian's saga architecture.
  • Enforce style guidelines, reusable patterns, and contract validation against handlers registry.
  • Use cases include creating new domain templates, extending existing sagas, and validating script templates before deployment.

Quick Start

Create a new saga template by specifying the domain and operation, then run the generator.

Frequently Asked Questions about starlark-saga-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate type-safe Starlark saga scripts for distributed transactions?

You can generate type-safe Starlark saga scripts by specifying the domain and operation, then running the generator to automate template creation, syntax enforcement, and contract validation against the handlers registry.

What is a Starlark saga script and when do I need one for transaction orchestration?

A Starlark saga script orchestrates distributed transactions deterministically. You need one when coordinating multi-step operations across services to ensure consistent syntax, input validation, and alignment with the saga service catalog.

How do I validate existing saga scripts against the handlers registry before deployment?

You validate existing saga scripts by running the template verification process, which checks your scripts against saga contracts and the handlers registry to ensure compliance with architecture docs before deployment.

Can I extend an existing saga with new domain operations using this generation approach?

Yes, you can extend existing sagas by specifying the target domain and new operation, then running the generator to apply reusable patterns and style guidelines while maintaining contract validation against the handlers registry.

What are the limitations of automating Starlark saga script generation for Meridian workflows?

Generation is scoped to common use cases like new domain templates, saga extensions, and template verification. It enforces deterministic templates and style guidelines but requires alignment with Meridian's specific saga service catalog and architecture.

Does Starlark saga generation work without manual coding for new domain templates?

Yes, Starlark saga generation minimizes manual coding by automating template scaffolding, enforcing reusable patterns, and validating inputs against the handlers registry to produce deterministic, type-safe scripts for new domain templates.