CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/paypal-sandbox

Wraps PayPal Sandbox testing patterns: sandbox account creation (Business + Personal accounts in developer.paypal.com), the Orders v2 API (create / capture / refund), webhook event simulator (developer.paypal.com webhook simulator), sandbox-account-specific test cards, and the OAuth2 client-credentials flow for sandbox. Use when testing PayPal-integrated code.

73

Quality

92%

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

Overview
Quality
Evals
Security
Files

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and token-efficient, with executable code throughout. It is held back by an implicit validation structure and a monolithic single-file layout with no bundle split.

Suggestions

Add explicit validation checkpoints (e.g., 'assert CREATED before capture; if status mismatch, re-check buyer approval') to turn the embedded expect() calls into a visible validate→fix→retry loop.

Move the larger reference material (full webhook signature verification, test-card catalog, anti-patterns) into files under references/ and link to them one level deep, so SKILL.md stays a lean overview.

Either create the referenced companion/sibling catalog files (payment-flow-states-reference, pci-dss-scope-reference, etc.) or drop the catalog references to avoid dangling pointers.

DimensionReasoningScore

Conciseness

Lean and mostly code/commands/tables with minimal prose; does not explain concepts Claude already knows (no 'what is OAuth/PayPal' padding). Every section earns its place for this multi-faceted skill.

3 / 3

Actionability

Provides copy-paste-ready TypeScript (OAuth client, OrdersCreateRequest, OrdersCaptureRequest, verifyWebhookSignature), bash install/curl, a test-card table, and CI YAML — concrete and executable, with only a minor `...` placeholder in the webhook-simulate curl.

3 / 3

Workflow Clarity

A logical setup→install→auth→create→capture→webhook sequence exists and code embeds expect() assertions, but there is no explicit validate→fix→retry feedback loop or framed checkpoint narrative as the score-3 anchor requires.

2 / 3

Progressive Disclosure

Sections are well-organized and external-doc references are clearly signaled and one level deep, but the entire body is a monolithic inline SKILL.md (~195 lines) with no bundle files, and the named companion/sibling catalogs are referenced yet do not exist in the bundle.

2 / 3

Total

10

/

12

Passed

Description

100%

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 precise, third-person description that names concrete actions, supplies an explicit use-when trigger, and carves out a distinct niche. It is a strong exemplar of the description rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'sandbox account creation (Business + Personal accounts)', 'Orders v2 API (create / capture / refund)', 'webhook event simulator', 'sandbox-account-specific test cards', 'OAuth2 client-credentials flow'. Uses third person ('Wraps'), so no voice penalty.

3 / 3

Completeness

Clearly answers 'what' with the enumerated capabilities and 'when' via the explicit trigger 'Use when testing PayPal-integrated code.'

3 / 3

Trigger Term Quality

Includes natural terms a user would say — 'PayPal Sandbox', 'testing PayPal-integrated code', 'webhook' — alongside specific API references, giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (PayPal Sandbox testing) with PayPal-specific triggers, making it unlikely to fire for unrelated payment skills.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents