CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/refund-test-matrix-builder

Workflow-driven skill that builds a refund test matrix from a payment-flow inventory: refund variants (full / partial / multiple-partials / over-refund / refund-on-disputed / refund-on-already-refunded), per-gateway nuances (Stripe, Adyen, PayPal, Braintree refund APIs), and timing variants (immediate / next-day / declined-by-bank), one test case per cell. Use for refund coverage on a new integration; for chargeback / dispute coverage use chargeback-flow-test-author, for webhook redelivery + idempotency use payment-webhook-replay, and for the state model use payment-flow-states-reference.

73

Quality

92%

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

80%

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

The content is highly actionable and concise with strong per-gateway code and a clear step sequence, but it lacks a validation checkpoint for its batch test-generation workflow and does not split its sizable per-gateway detail into local reference files.

Suggestions

Add an explicit validation step after Step 5/6 (e.g., run the generated test suite and confirm every (gateway, variant, timing) cell passes before reporting coverage) to lift workflow clarity.

Move the per-gateway refund patterns (Stripe/Adyen/PayPal/Braintree) into separate reference files under references/ and link to them one level deep, keeping SKILL.md an overview.

Either remove the companion-skill references that have no corresponding bundle files, or add those files so the References section points to real local resources.

DimensionReasoningScore

Conciseness

The body is lean — brief overview, tables, and executable per-gateway code with no explaining of concepts Claude already knows (e.g., what a refund is); nearly every token earns its place despite some repetition across the four gateway code blocks.

3 / 3

Actionability

Provides concrete executable TypeScript for each gateway, a specific grep command, a YAML test-matrix template, and copy-paste-ready tests with precise assertions, matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced, but generating a test matrix is a batch operation with no explicit validation/verification checkpoint (e.g., running the tests to confirm each cell passes), which per the rubric caps workflow clarity at 2.

2 / 3

Progressive Disclosure

No references/ scripts/ or assets/ bundle directories exist, yet the body references companion skills and external docs rather than real local files; the ~247-line body keeps per-gateway detail inline that could be split into reference files, so structure is only partially realized.

2 / 3

Total

10

/

12

Passed

Description

100%

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 highly specific, well-scoped description that clearly states both what the skill does and when to use it, with explicit hand-offs to sibling skills that reduce conflict risk. It uses third person and avoids vague language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and cells: refund variants (full / partial / multiple-partials / over-refund / refund-on-disputed / refund-on-already-refunded), per-gateway refund APIs, timing variants, and 'one test case per cell' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (builds a refund test matrix from a payment-flow inventory) and 'when' via an explicit 'Use for refund coverage on a new integration' clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say ('refund coverage', 'new integration', 'chargeback', 'dispute', 'webhook redelivery + idempotency'), giving good coverage of natural trigger language.

3 / 3

Distinctiveness Conflict Risk

Clear niche (refund test matrix) with distinct triggers, and it explicitly hands off adjacent scopes to named sibling skills (chargeback-flow-test-author, payment-webhook-replay, payment-flow-states-reference), actively reducing conflict risk.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents