paddle-sandbox-testing

Test a Paddle integration end-to-end using the sandbox environment, test cards, the webhook simulator, and local tunnels — without taking real money.

Quality

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/sandbox-testing/SKILL.md

Quality

Content

77%

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

This is a solid, actionable skill that provides concrete guidance for testing a Paddle integration end-to-end. Its main strengths are the specific test card numbers, executable code examples, and the well-structured end-to-end verification workflow with explicit checkpoints. Its weakness is length — the MCP server block quote, the detailed sandbox-vs-live comparison tables, and some repeated advice in the pitfalls section make it longer than necessary for a skill file.

Suggestions

Move the MCP server usage block quote to a separate reference file — it's a tangential topic that adds significant length and breaks the flow of the testing workflow.

Consider extracting the 'Sandbox vs live: differences that may catch you out' table into a separate reference file and linking to it, keeping only a brief summary inline.

Dimension	Reasoning	Score
Conciseness	The skill is generally well-structured but includes some unnecessary verbosity — the sandbox vs production table is quite detailed, the MCP server block quote is a large tangent, the 'common pitfalls' section repeats points already covered, and some explanatory prose could be trimmed. However, it avoids explaining basic concepts Claude would know.	2 / 3
Actionability	Provides concrete test card numbers, exact environment variable names with prefixes, executable code for the simulator API, specific CLI commands for tunneling, and a step-by-step end-to-end test flow. Everything is copy-paste ready and specific.	3 / 3
Workflow Clarity	The end-to-end test in Step 5 is a clear numbered sequence with explicit validation checkpoints ('Confirm' steps checking browser, server logs, DB rows, and dashboard). The overall flow from setup through testing to verification is well-sequenced with feedback loops (signature verification failure troubleshooting, re-checking after cancellation).	3 / 3
Progressive Disclosure	The skill references related skills (checkout-web, webhooks, subscription-sync, catalog-setup) and external docs, which is good. However, the content is quite long and monolithic — the sandbox vs live differences table, the MCP server usage block, and the common pitfalls section could potentially be split into separate reference files. Without bundle files, the inline content is heavier than ideal for a SKILL.md overview.	2 / 3
	Total	10 / 12 Passed

Description

82%

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

This is a strong, specific description that clearly identifies the domain (Paddle payment integration testing) and lists concrete tools and techniques involved. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are excellent and highly specific to the domain.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to test Paddle payments, set up a Paddle sandbox, simulate webhooks, or verify a Paddle integration without processing real transactions.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: testing Paddle integration end-to-end, using sandbox environment, test cards, webhook simulator, and local tunnels. Also specifies the constraint 'without taking real money.'	3 / 3
Completeness	Clearly answers 'what does this do' (test a Paddle integration using sandbox, test cards, webhook simulator, local tunnels), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Paddle', 'sandbox', 'test cards', 'webhook simulator', 'local tunnels', 'end-to-end', and 'integration'. These are terms a developer working with Paddle payments would naturally use.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche — specifically about Paddle payment integration testing with sandbox tools. Unlikely to conflict with other skills due to the specificity of 'Paddle', 'sandbox environment', 'test cards', and 'webhook simulator'.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Commit: 72e6fdf

Reviewed: 20 days 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.