saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.
Overall
score
73%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.43xAgent success when using this skill
Validation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with explicit 'Use when' guidance and a distinct technical niche. However, it relies heavily on technical jargon without concrete action examples, which may limit discoverability for users who describe their needs in more natural language. The specificity could be improved by listing concrete implementation actions.
Suggestions
Add concrete actions like 'create saga orchestrators', 'define compensation handlers', 'implement rollback logic', or 'track saga state'
Include more natural trigger terms users might say such as 'rollback', 'multi-service transaction', 'eventual consistency', or 'transaction failure'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (saga patterns, distributed transactions) and some actions (coordinating, handling, managing), but lacks concrete specific actions like 'create saga orchestrators', 'define compensation logic', or 'implement rollback handlers'. | 2 / 3 |
Completeness | Clearly answers both what ('Implement saga patterns for distributed transactions and cross-aggregate workflows') and when ('Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'saga patterns', 'distributed transactions', 'compensating transactions', and 'long-running workflows', but these are somewhat technical. Missing more natural user terms like 'rollback', 'multi-service coordination', 'eventual consistency', or 'transaction failure handling'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'saga patterns', 'distributed transactions', 'cross-aggregate workflows', and 'compensating transactions' creates a clear niche that is unlikely to conflict with general workflow or transaction skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable saga pattern implementations with good code quality and multiple approaches (orchestration, choreography, timeouts). However, it's verbose for a skill file, includes explanatory content Claude doesn't need, and lacks explicit workflow documentation with validation checkpoints for what is inherently a complex, failure-prone distributed systems pattern.
Suggestions
Add an explicit workflow section with numbered steps and validation checkpoints for implementing and testing sagas, especially around compensation testing
Move detailed templates to separate reference files (e.g., ORCHESTRATOR.md, CHOREOGRAPHY.md) and keep SKILL.md as a concise overview with quick-start example
Remove the 'When to Use This Skill' and 'Core Concepts' sections - Claude understands saga patterns; focus on the actionable templates
Add explicit verification steps: 'After implementing compensation, test by forcing failure at each step and verifying rollback completes correctly'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the 'When to Use This Skill' section listing obvious use cases, and the Core Concepts section explaining saga types with ASCII diagrams that Claude likely already understands. The templates themselves are well-structured but verbose. | 2 / 3 |
Actionability | Provides fully executable Python code templates with complete class implementations, concrete examples of order fulfillment sagas, event handlers, and compensation logic. The code is copy-paste ready with clear patterns for both orchestration and choreography approaches. | 3 / 3 |
Workflow Clarity | The saga execution flow is implicit in the code rather than explicitly documented as a workflow. While the code shows compensation handling, there are no explicit validation checkpoints or verification steps documented. The state transitions are shown in a table but not as an actionable workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but is monolithic - all templates are inline rather than referenced. The Resources section links to external materials, but there's no internal file structure suggested for organizing the extensive code templates. The 400+ lines could benefit from splitting into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.