Name: testland/idempotency-test-author
Rating: 87.8 (1 reviews)
Author: testland

testland/idempotency-test-author

Build-an-X for idempotency tests in any async/job/API context - idempotency-key handling (per Stripe / AWS prescriptive guidance pattern), retry-safe semantics (exactly-once vs at-least-once vs at-most-once), side-effect commutativity verification, fingerprint-based dedup, idempotency-window tuning. Use when authoring tests for any system where the same input could be processed twice (SQS Standard at-least-once, RabbitMQ requeue, retry-on-error logic, webhook redelivery, browser double-click, mobile-network retry).

1.01x

Quality

86%

Does it follow best practices?

Impact

95%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

78%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, actionable skill body with executable test templates, a clear stepwise workflow, and clean one-level-deep progressive disclosure. The main gaps are minor: some Overview/Step-7 redundancy, undefined fixture/helper references in code snippets, and no explicit failure-recovery guidance for the harder tests.

Suggestions

Tighten redundancy: trim the Overview to not restate the description, and make Step 7 a pure checklist of test names rather than re-describing each step.

Add a brief note (or fixture stub) defining the helpers the snippets assume (process_charge, charge_processor, store, endpoint, freezer, IdempotencyConflictError) so the patterns are closer to copy-paste executable.

Add a short troubleshooting note for the concurrent-duplicate test (the hardest case), e.g. how to interpret a flaky/failing race test, to supply the missing error-recovery feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable code and tables rather than concept re-explanation, but the Overview restates the description and Step 7's checklist re-lists Steps 2/3/5/6, introducing minor redundancy that keeps it below a 5.	4 / 5
Actionability	Provides several concrete, template-ready test patterns (duplicate-key, body-mismatch rejection, TTL expiry, concurrent duplicate) covering the common cases, but snippets reference undefined helpers/fixtures (process_charge, charge_processor, store, endpoint, freezer, IdempotencyConflictError) a user must wire up.	4 / 5
Workflow Clarity	Clear Step 1→7 sequence with a Step 1 classification decision table and a Step 7 end-to-end ✅ checklist; this is a test-authoring skill so the destructive/batch cap-3 rule does not apply, but no explicit error-recovery feedback loop (e.g. flaky concurrent test → debug path) is given.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep links to references/idempotency-patterns.md at Step 4 and Step 6 (verified to exist), and the split is sensible — advanced commutativity and race patterns live in the reference while the core key pattern stays inline.	5 / 5
	Total	17 / 20 Passed

Description

88%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 with explicit what/when structure and concrete trigger scenarios. The main defect is the 'Build-an-X for' template-artifact opener, which reads as an unfilled placeholder rather than a real capability verb.

Suggestions

Replace the 'Build-an-X for' placeholder opener with a concrete third-person verb phrase, e.g. 'Authors idempotency tests for any async/job/API context'.

Add a couple of plain-language trigger synonyms ('duplicate request', 'redundant processing') alongside the delivery-semantics terms to broaden natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	Enumerates five concrete techniques (idempotency-key handling, retry-safe semantics, side-effect commutativity verification, fingerprint-based dedup, idempotency-window tuning) — comprehensive coverage with no gaps; the awkward 'Build-an-X for' opener is a template artifact but does not undercut the concrete capability list.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated idempotency techniques) and 'when' ('Use when authoring tests for any system where the same input could be processed twice (...)') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage (SQS Standard at-least-once, RabbitMQ requeue, webhook redelivery, browser double-click, mobile-network retry); falls short of 5 because common phrases like 'duplicate request' / 'redundant processing' are absent and 'Build-an-X' is not a user utterance.	4 / 5
Distinctiveness Conflict Risk	'idempotency tests' is a clear niche with specific triggers, but sibling test-authoring skills it itself references (sqs-tests, rabbitmq-tests, cron-job-test-author) create minor overlap risk rather than minimal.	4 / 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.

Reviewed

3 days ago

Table of Contents

Discovery Implementation Validation