CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/saga-transaction-tests

Build saga transaction tests - orchestration vs choreography variants, per-step compensating-action verification, partial-failure scenarios (Step 3 fails → Steps 1+2 must compensate), idempotency of compensations, outbox pattern for atomic DB-update + message-publish. Per microservices.io/saga; tests guard against ACD-without-Isolation anomalies. Use when a business transaction spans two or more services and the compensating paths for a mid-sequence failure have no coverage, or right after compensation logic changes.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

82%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.

A well-structured, highly actionable testing recipe with executable code in every step and a clear failure-matrix workflow. Minor gaps in conciseness (some restating) and an absent validate-fix-retry loop keep it just short of top marks.

Suggestions

Trim the opening saga definition and 'When to use' bullets, which restate the frontmatter description and add tokens Claude doesn't need.

Add a short 'run the matrix, if a test fails fix the compensation then re-run' feedback loop to make the validate->fix->retry cycle explicit.

Consider moving the per-step code templates into a references/ file so SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient, code-forward content with brief per-step context, but includes mild over-explanation (the opening saga definition and a 'When to use' section that restates the description).

4 / 5

Actionability

Every step provides complete, executable pytest code with mock setup and assertions - happy path, parametrized failures, idempotency, outbox, choreography fan-out, and timeout - copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with a stated failure-points x compensation matrix and an anti-patterns error-recovery table, but no explicit validate->fix->retry loop tying test failure back to saga repair.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a signaled References list; no bundle files exist so nothing is split into deeper files, and the length is all inline (appropriate for a pattern recipe but monolithic).

4 / 5

Total

17

/

20

Passed

Description

100%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 strong, specific description that clearly states what the skill does and when to use it, with comprehensive trigger terms and a distinct niche. Third-person/imperative voice is used correctly throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'orchestration vs choreography variants', 'per-step compensating-action verification', 'partial-failure scenarios', 'idempotency of compensations', 'outbox pattern' - giving comprehensive coverage of the saga-testing domain.

5 / 5

Completeness

Explicitly answers both what (build saga transaction tests with the listed variants) and when ('Use when a business transaction spans two or more services and the compensating paths...have no coverage, or right after compensation logic changes') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms a developer would say - 'saga', 'distributed-transaction', 'compensating-transaction', 'orchestration', 'choreography', 'compensating paths', 'partial-failure'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (saga transaction testing) with distinct triggers; sibling skills (event-sourcing-tests, mvcc-isolation-tests) are explicitly differentiated, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents