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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

88%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 highly actionable, well-sequenced skill with concrete code, test cards, and explicit validation checkpoints throughout. It is on the verbose side and fully inlines content rather than splitting detail into bundle files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the ~175-line body has some trimmable explanation (the extended MCP sidebar and repeated sandbox/live separation notes) that could be tightened.	4 / 5
Actionability	Copy-paste ready throughout: concrete env vars, exact test card numbers, dashboard navigation paths, an executable simulator snippet, hookdeck commands, and a full end-to-end test loop covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence (configure → test cards → simulator → tunnel → end-to-end test) with explicit 'Confirm' validation checkpoints and expected state assertions, plus a pitfalls section for error recovery.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep links to external Paddle docs and no nested references, but the body is long and entirely inlined with no bundle files to offload detail.	4 / 5
	Total	18 / 20 Passed

Description

75%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 specific, distinctive description that names concrete testing surfaces clearly, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 3. Adding a natural trigger phrase would lift the score meaningfully.

Suggestions

Append an explicit trigger clause, e.g. 'Use when verifying a Paddle integration before going live — running sandbox checkouts, firing webhook events, or testing subscription state changes.'

Add a couple of common user synonyms (e.g. 'staging', 'go-live', 'webhook testing') to broaden natural trigger coverage.

Keep the third-person voice but ensure the 'when to use' guidance is as concrete as the 'what' already is.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete testing surfaces — 'sandbox environment, test cards, the webhook simulator, and local tunnels' — with comprehensive coverage of the end-to-end testing domain.	5 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no explicit 'Use when...' trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('Paddle integration', 'sandbox', 'test cards', 'webhook simulator', 'local tunnels') but a few common user phrases (e.g. 'go-live', 'staging', 'webhook testing') are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Paddle sandbox end-to-end testing — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 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.

Repository: PaddleHQ/paddle-agent-skills
Path: skills/sandbox-testing/SKILL.md
Commit: de7fcd3

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.