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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/sandbox-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 guide with explicit validation checkpoints and error-recovery loops, covering dashboard, MCP, and CLI paths with copy-paste commands. Its weaknesses are the two general-purpose MCP/CLI digressions that pad the token budget, and the absence of any reference files — detailed tables that belong in references/ are all inlined in a single long SKILL.md.

Suggestions

Trim or relocate the general Paddle MCP conventions blockquote (camelCase methods, pagination, tool caps) and general CLI usage notes — they are not sandbox-testing-specific — into a shared reference file or sibling skill.

Split stable lookup material into references/ (e.g. references/test-cards.md, references/simulator-scenarios.md, references/sandbox-vs-live.md) and keep SKILL.md as the workflow overview with well-signaled one-level-deep links.

Convert sibling-skill mentions (checkout-web, catalog-setup, subscription-cancel) into clearly signaled cross-references so the navigation intent is explicit.

DimensionReasoningScore

Conciseness

Mostly dense Paddle-specific facts Claude doesn't know (refund approval timing, retry counts, sandbox email routing), but the two long blockquotes on general Paddle MCP conventions and general CLI usage are digressions not specific to sandbox testing, and the 230-line body could be tightened. Not a 2 because the bulk earns its place; not a 4 because the digressions are more than minor.

3 / 5

Actionability

Copy-paste ready throughout: exact test card numbers, a .env block, an executable MCP async function, concrete CLI commands with --json bodies, a runnable CI bash script with status polling, and exact dashboard paths and API method names. Coverage spans dashboard, MCP, and CLI paths for each operation.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced, and the end-to-end loop (Step 5) has explicit "Confirm" checkpoints plus expected event sequences for each cancel path. Error recovery is spelled out (signature mismatch → secret diagnosis, checkout_url_domain_not_approved → add domain and retry, aborted events → destination usage-type fix), and the CI example fails the build on undelivered events.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all ~230 lines — including a test-card table, a simulator scenario reference, general MCP/CLI conventions, and a sandbox-vs-live diff table that would fit separate reference files — are inlined in one SKILL.md. Section structure is good, but content that should be split is inline and the sibling-skill mentions (checkout-web, catalog-setup) are not navigable references.

3 / 5

Total

16

/

20

Passed

Description

70%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 the domain and its concrete mechanisms with natural trigger terms, but it lacks any "Use when..." trigger clause, capping completeness. Adding explicit trigger guidance (e.g. "Use when verifying a Paddle integration before going live") would lift it to the top anchor.

Suggestions

Append an explicit trigger clause, e.g. "Use when testing or verifying a Paddle integration, before going live, or when the user mentions sandbox, test cards, or webhook testing."

Include natural synonym phrases users might say — "test payments", "staging", "go-live checklist" — alongside the existing trigger terms.

Consider naming one or two concrete actions beyond "Test" (e.g. "run test checkouts and trigger webhook events") to strengthen the action enumeration.

DimensionReasoningScore

Specificity

"Test a Paddle integration end-to-end using the sandbox environment, test cards, the webhook simulator, and local tunnels" names the domain plus four concrete mechanisms. Not a 5 because it uses a single action verb ("Test") and enumerates tools rather than multiple distinct actions; clearly above 3's 1–2 concrete actions.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance — "without taking real money" only weakly implies pre-launch verification, so per the judging guidelines completeness is capped at 3. Not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Natural developer terms are present — "Paddle", "sandbox", "test cards", "webhook", "local tunnels", "end-to-end" — matching what a user would actually say. A 5 would require synonyms/variations (e.g. "test payments", "staging", "go live"), which are missing.

4 / 5

Distinctiveness Conflict Risk

"Paddle integration... sandbox environment, test cards, the webhook simulator" carves out a clear niche with distinct triggers; no realistic overlap with other skills' descriptions.

5 / 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

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.