SKILLEMALL.ai
GitHub ↗ RU Sign in

AC payment-testing

Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle simulation, webhook testing (stripe listen/trigger, signature verification, idempotency), failed/retried payments and refunds, and never using real cards. Use when: "test Stripe checkout," "payment test," "3DS test," "test webhook signature," "test subscription renewal," "test clock," "refund test," "decline card test," "checkout E2E." Not for: General API contract testing of non-payment endpoints — api-testing. PCI-DSS/regulatory compliance audit — compliance-testing. Related: api-testing, playwright-automation, compliance-testing, test-data-management, qa-project-context.

petrkindlmann/qa-skills Agent Skills author: petrkindlmann MIT 5 files body ≈ 4 620 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal.

As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions

IntegrationPlaywrightStripeCommerceSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
95
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
Result and completion w 14
40
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 61/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Execution cost. Instruction body is 4620 tokens
    • 100Steps. 46 steps
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 15 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +3Description length 892: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 9 example trigger phrases
    • +4Description says when NOT to use the skill
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 46 items
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.