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

74%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/sandbox-testing/SKILL.md

Quality

Discovery

72%

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

The description effectively identifies a clear niche (Paddle payment integration testing) with good trigger terms that developers would naturally use. However, it lacks an explicit 'Use when...' clause and could benefit from listing more concrete actions beyond the general 'test end-to-end' framing.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to test Paddle payments, subscriptions, webhooks, or checkout flows in a sandbox environment.'

List more specific concrete actions, e.g., 'Set up sandbox credentials, create test subscriptions, simulate webhook events, verify payment flows, and debug checkout integration.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Paddle integration testing) and mentions specific tools (sandbox environment, test cards, webhook simulator, local tunnels), but doesn't list concrete actions beyond 'test end-to-end'. It lacks specifics like 'create test subscriptions', 'verify webhook payloads', or 'simulate payment failures'.	2 / 3
Completeness	The 'what' is present (test a Paddle integration end-to-end using specific tools), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the nature of the task description.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Paddle', 'sandbox', 'test cards', 'webhook simulator', 'local tunnels', 'end-to-end', and 'without taking real money'. These cover the terms a developer would naturally use when seeking help with Paddle testing.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — 'Paddle integration' combined with 'sandbox environment', 'test cards', and 'webhook simulator' creates a very clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

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 strong, 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 main weakness is length — several sections (the MCP tangent, the detailed sandbox-vs-live tables) could be extracted to supporting files to improve token efficiency.

Suggestions

Extract the MCP server usage block and the sandbox-vs-live differences table into separate reference files to reduce the main skill's token footprint.

Trim the 'When to use this skill' section — the first sentence suffices; the rest restates what the skill title already conveys.

Dimension	Reasoning	Score
Conciseness	The skill is generally well-structured but includes some unnecessary verbosity — the sandbox vs production table is quite detailed for information Claude could infer, the MCP server block is a large tangent, and the 'Common pitfalls' section restates some points already covered. The 'When to use this skill' section also over-explains. However, most content earns its place.	2 / 3
Actionability	Provides concrete, copy-paste-ready content throughout: specific env variable names with prefixes, exact test card numbers with expected outcomes, executable JS code for the simulator API, specific CLI commands for tunneling, and a step-by-step end-to-end test flow with explicit verification points.	3 / 3
Workflow Clarity	The end-to-end test in Step 5 is a clear numbered sequence with explicit validation checkpoints (confirm browser redirect, check server logs, verify DB rows, check dashboard). The overall 5-step structure progresses logically from setup through testing, and Step 7 includes verification of state transitions. Error recovery is addressed via the simulator for failure paths.	3 / 3
Progressive Disclosure	The skill references related skills (checkout-web, webhooks, subscription-sync, catalog-setup) and links to 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 detailed simulator instructions could be split into separate reference files. Without bundle files, all content is inline in one large document.	2 / 3
	Total	10 / 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: 86596b3

Reviewed: 16 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.