CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is paddle-sandbox-testing in PaddleHQ/paddle-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An exceptionally actionable, well-sequenced testing guide with strong validation checkpoints and failure-path coverage — nearly every token carries non-obvious operational knowledge. The main structural weakness is the total absence of bundle files: reference material like the test-card list, simulator scenario table, and generic MCP/CLI usage notes are inlined rather than split into one-level-deep references.

Suggestions

Split stable reference material into bundle files — e.g. `references/test-cards.md` (full card list), `references/simulator-scenarios.md` (scenario/event tables and options), and `references/paddle-mcp-cli.md` (the generic MCP and CLI usage blockquotes) — keeping SKILL.md as the workflow overview.

Signal each split file clearly from the relevant step (e.g. "Full scenario reference: see simulator-scenarios.md") so navigation stays one level deep.

Move the version-pinned CLI details ("v0.2.0 or later") into the CLI reference file or a versioning note so the time-sensitive pin doesn't age the core workflow.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious Paddle-specific facts (key prefixes, retry windows, destination usage types, email-delivery quirks) and assumes Claude's competence rather than explaining basics. It falls short of anchor 5 due to the version-pinned CLI note ("v0.2.0 or later") and two long blockquotes of generic Paddle MCP/CLI usage that could be trimmed or shared.

4 / 5

Actionability

Fully executable throughout: exact test card numbers, a ready-to-run MCP `execute` snippet, CLI commands with `--json` bodies, a complete CI polling script that fails on undelivered events, an `.env` snippet, and exact dashboard navigation paths and API key permission names. Copy-paste ready and covers the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence plus an end-to-end test loop with explicit confirmation checkpoints per cancellation mode (expected event sequences for real vs. simulated, immediate vs. next-period). Error recovery is spelled out (`checkout_url_domain_not_approved` handling, CLI exit codes 5/7, webhook secret mismatch, aborted simulation events) and the CI section gates on delivery status.

5 / 5

Progressive Disclosure

Sections are well-organized with a "Related docs" list and cross-links to sibling skills, but the bundle contains no reference files at all: reference material (the full test-card list, the simulator scenario table, and the generic Paddle MCP/CLI usage blockquotes) is inlined in a ~230-line SKILL.md. This fits anchor 3 (content that should be separate is inline) better than anchor 4, since no detail is offloaded to a one-level-deep bundle file.

3 / 5

Total

17

/

20

Passed

Description

71%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, concrete, third-person description that clearly states what the skill does and is well distinguished from other domains. Its main weakness is the absence of any explicit "Use when..." trigger clause, which both caps completeness and leaves trigger-term coverage short of comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when verifying a Paddle integration before going live, or when the user mentions sandbox testing, test cards, webhook simulation, or tunneling localhost for webhooks."

Include a few more natural synonyms users would say, such as "webhook testing", "test my Paddle integration", or "go-live checklist", to raise trigger-term coverage.

Mention checking sandbox-vs-live behavioral differences (refunds, retries, domain approval) in the description so users hitting production-mismatch bugs find this skill.

DimensionReasoningScore

Specificity

"Test a Paddle integration end-to-end using the sandbox environment, test cards, the webhook simulator, and local tunnels" names multiple concrete components (sandbox, test cards, simulator, tunnels) that comprehensively match the skill's actual scope, with "without taking real money" adding a precise qualifier. This matches the comprehensive-coverage anchor better than anchor 4, which anticipates gaps.

5 / 5

Completeness

The "what" is clear (end-to-end Paddle integration testing via sandbox, test cards, simulator, tunnels), but there is no "Use when..." clause or equivalent explicit trigger guidance — "without taking real money" is a qualifier, not a trigger. Per the rubric guideline, a missing explicit trigger caps completeness at 3; it is not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural user phrases are present — "Paddle", "sandbox", "test cards", "webhook", "simulator", "tunnel", "end-to-end" — but common variations like "webhook testing", "go live", or tool names like "ngrok" are missing. Good coverage per anchor 4, short of the synonym- and extension-level completeness of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Paddle" plus "sandbox", "test cards", and "webhook simulator" carves a clear niche with mostly distinct triggers. Minor overlap risk remains with closely related Paddle sibling skills (e.g. a user saying "test webhooks" could match a `webhooks` skill), fitting anchor 4 better than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PaddleHQ/paddle-agent-skills

Path

providers/codex/plugin/skills/sandbox-testing/SKILL.md

Reviewed

Table of Contents

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.