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.
78
66%
Does it follow best practices?
Impact
100%
1.33xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/saga-orchestration/SKILL.mdQuality
Discovery
89%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 is a solid skill description that clearly identifies a specific architectural pattern domain and provides explicit trigger guidance via a 'Use when' clause. The trigger terms are well-chosen and domain-appropriate. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating orchestrators, defining compensation logic, implementing retry policies).
Suggestions
Expand the capability list with more concrete actions, e.g., 'create saga orchestrators, define compensation steps, implement retry and timeout policies, generate state machines for workflow coordination'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (saga patterns, distributed transactions) and some actions (coordinating, handling compensating transactions, managing workflows), but doesn't list multiple concrete specific actions like 'create saga orchestrators, define compensation steps, implement timeout handling'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement saga patterns for distributed transactions and cross-aggregate workflows) and 'when' (explicit 'Use when' clause covering coordinating multi-step processes, handling compensating transactions, managing long-running workflows). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'saga patterns', 'distributed transactions', 'cross-aggregate workflows', 'compensating transactions', 'long-running workflows', 'multi-step business processes'. These cover the key vocabulary a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Saga patterns and distributed transactions are a very specific niche within software architecture. The trigger terms are distinct and unlikely to conflict with general workflow, transaction, or process management skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable Python code for saga patterns, which is its primary strength. However, it is far too verbose for a SKILL.md - it dumps ~350 lines of code templates inline without progressive disclosure, includes conceptual explanations Claude doesn't need, and lacks explicit workflow guidance for actually implementing and validating a saga in a real project. The content would benefit greatly from splitting templates into separate files and adding a concise implementation workflow.
Suggestions
Move Templates 2-4 into separate referenced files (e.g., examples/order_saga.py, examples/choreography.py) and keep only Template 1 (the base orchestrator) inline with a brief summary of each pattern variant.
Remove the 'Core Concepts' section (saga types diagram, execution states table) - Claude already knows these concepts; the code itself demonstrates them.
Add an explicit implementation workflow with validation steps, e.g.: '1. Define steps with actions and compensations → 2. Implement each service handler → 3. Test compensation path by forcing failures at each step → 4. Verify idempotency by replaying events'.
Condense the Best Practices into the workflow or remove obvious advice (e.g., 'Log everything', 'Use correlation IDs') that Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It includes unnecessary concept explanations (saga types, execution states table) that Claude already knows, and the ASCII diagram adds little value. The four full templates are largely redundant - Template 2 is a straightforward extension of Template 1, and Template 4 is a minor variation. Much of this could be condensed significantly. | 1 / 3 |
Actionability | The code templates are fully executable Python with complete class definitions, concrete method implementations, and realistic usage examples. The order fulfillment saga shows both the orchestrator definition and the service-side event handlers, making it copy-paste ready. | 3 / 3 |
Workflow Clarity | The saga execution flow is implicit in the code rather than explicitly documented as a step-by-step workflow. While the compensation logic is present in code, there are no explicit validation checkpoints or verification steps for implementing/testing a saga. The 'Don't skip compensation testing' advice is vague with no concrete testing approach. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of code with four large templates all inline. The templates should be split into separate files (e.g., ORCHESTRATOR.md, CHOREOGRAPHY.md, TIMEOUTS.md) with SKILL.md providing a concise overview and links. The Resources section links to external sites but doesn't organize the internal content across files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.