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.

1.33x

Quality

76%

Does it follow best practices?

Impact

100%

1.33x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/saga-orchestration/SKILL.md

The canonical home for this skill is saga-orchestration in wshobson/agents

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Actionable and well-structured with strong executable templates, but the body is heavy for a SKILL.md overview and relies on inline code rather than one-level-deep reference files. Adding an explicit deploy/run workflow with validation checkpoints and splitting templates into reference files would raise the weaker dimensions.

Suggestions

Move the four code templates into separate reference files (e.g. references/orchestrator_base.py, references/order_fulfillment.py) and link to them from SKILL.md to improve progressive disclosure and reduce token load.

Add an explicit numbered workflow (define steps -> start saga -> handle step completion/failure -> compensate -> verify final state) with validation checkpoints for the compensating/rollback path, which currently lives only implicitly in code.

Trim the inline orchestrator base template to its essential skeleton in SKILL.md, keeping the full implementation in a reference file, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no padding of basic concepts, but ~480 lines including four full inline templates (the orchestrator base alone is ~190 lines) is more than a SKILL.md overview needs and could be tightened by offloading templates to reference files.	3 / 5
Actionability	Four complete, copy-paste-ready Python templates (orchestrator base, order fulfillment, choreography, timeouts) cover the common cases with executable code and concrete usage examples, matching the top anchor.	5 / 5
Workflow Clarity	The saga lifecycle sequence exists only implicitly inside the code (start -> handle completion/failure -> compensate), with no explicit numbered workflow or validation checkpoints; given sagas involve rollback/compensating (quasi-destructive) operations, the missing explicit checkpoints cap this at 3.	3 / 5
Progressive Disclosure	Section structure is clear (When to Use, Core Concepts, Templates, Best Practices, Resources) but no bundle/reference files exist, and the four large templates that clearly belong in separate files are inlined, fitting the 'content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that uses third-person voice, names a distinct niche, and explicitly pairs a concrete 'what' with a trigger-laden 'when' clause. Minor additional synonyms would push trigger coverage to the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Implement saga patterns', 'coordinating multi-step business processes', 'handling compensating transactions', 'managing long-running workflows') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (Implement saga patterns for distributed transactions and cross-aggregate workflows) and 'when' (Use when coordinating multi-step business processes...) with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('saga patterns', 'distributed transactions', 'compensating transactions', 'long-running workflows') that a developer would plausibly say, but a few natural synonyms (e.g. 'rollback', 'event-driven transactions') are absent, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (saga orchestration for distributed transactions) with distinct triggers and minimal overlap with unrelated skills, matching the 'clear niche, minimal conflict risk' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/saga-orchestration/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.