CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

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-3

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 test data and validation checkpoints, held back from the top band by mild verbosity and inline content that could be factored into reference files.

Suggestions

Move the large sandbox-vs-production tables and the MCP tool-usage sidebar into a references/ file, keeping SKILL.md as a lean overview with one-level links.

Trim explanatory asides Claude already knows (e.g. 'Paddle gives you two completely separate environments') to tighten token efficiency.

Consider extracting the full test-card table to a reference doc and keeping only the canonical 4242 card inline.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with concrete tables, but it explains things Claude already knows ('Paddle gives you two completely separate environments') and the large MCP-method-path sidebar is padded; it could be tightened without losing clarity.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — exact test card numbers, env var names with key prefixes, API base URLs, a runnable simulator JS snippet, hookdeck commands, and a concrete end-to-end loop.

3 / 3

Workflow Clarity

The Step 1–Step 5 sequence and the numbered end-to-end test include explicit 'Confirm' validation checkpoints and a signature-mismatch diagnosis feedback loop, satisfying the anchor for clear sequencing with validation.

3 / 3

Progressive Disclosure

Well-organized with clearly signaled one-level external doc links, but it is a single ~180-line file with large inline tables and an MCP sidebar that could reasonably be split into reference files; no bundle files exist to offload detail.

2 / 3

Total

10

/

12

Passed

Description

82%Weight 40%Scale 1-3

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, well-triggered description with concrete capabilities and a clear niche, weakened only by the absence of an explicit 'Use when...' clause that would make the triggering condition unambiguous.

Suggestions

Add an explicit trigger clause, e.g. 'Use when verifying a Paddle integration before going live — running test checkouts, simulating webhooks, or checking sandbox-vs-live behavior.'

Mirror a couple of the body's natural trigger phrasings (e.g. 'go-live checklist', 'dunning', 'past_due') into the description to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the Paddle domain and multiple concrete actions — 'end-to-end', 'sandbox environment', 'test cards', 'webhook simulator', and 'local tunnels' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does but never gives an explicit 'Use when...' trigger clause, so the 'when' is only implied; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would actually say — 'Paddle integration', 'sandbox', 'test cards', 'webhook simulator', 'local tunnels', 'without taking real money' — giving good coverage rather than bare jargon.

3 / 3

Distinctiveness Conflict Risk

The Paddle-sandbox-testing niche is distinct and its triggers (sandbox, test cards, webhook simulator) are unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PaddleHQ/paddle-agent-skills
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.