paypal-integration
Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows.
83
63%
Does it follow best practices?
Impact
96%
1.03xAverage score across 6 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/payment-processing/skills/paypal-integration/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly communicates specific capabilities (express checkout, subscriptions, refund management), includes natural trigger terms users would employ, and explicitly states both what the skill does and when to use it. The PayPal-specific focus makes it highly distinctive and unlikely to conflict with other payment-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'express checkout', 'subscriptions', and 'refund management'. These are distinct, well-defined capabilities within PayPal payment processing. | 3 / 3 |
Completeness | Clearly answers both 'what' (integrate PayPal payment processing with express checkout, subscriptions, refund management) and 'when' (explicit 'Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'PayPal', 'payment processing', 'express checkout', 'subscriptions', 'refund', 'online transactions', 'e-commerce', 'checkout flows'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to PayPal specifically, which distinguishes it from other payment provider skills (e.g., Stripe). The combination of 'PayPal', 'express checkout', and 'subscriptions' creates a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly verbose and monolithic, spending significant tokens on concept explanations Claude doesn't need while lacking critical workflow validation steps for financial operations. The code examples are mostly concrete but have consistency issues (mixing deprecated SDK with REST API) and missing error handling for HTTP responses. The content would benefit greatly from being split into focused files with a lean overview.
Suggestions
Remove the 'Core Concepts' and 'When to Use This Skill' sections entirely—Claude knows what PayPal products are and when to use payment integration.
Add explicit HTTP status code checks after every API call and a clear end-to-end workflow with numbered steps and validation checkpoints (e.g., 'Verify order status is APPROVED before calling capture').
Split into separate files: keep SKILL.md as a concise overview with Quick Start, then reference SUBSCRIPTIONS.md, IPN.md, REFUNDS.md for detailed implementations.
Fix the Quick Start backend to use the v2 Orders API consistently with the frontend instead of the deprecated paypalrestsdk Payment class.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It includes unnecessary sections like 'When to Use This Skill' bullet lists, 'Core Concepts' that explain what PayPal Checkout, Subscriptions, and Payouts are (Claude already knows this), and redundant comments throughout the code. The 'Core Concepts' section is pure padding that describes rather than instructs. | 1 / 3 |
Actionability | The code examples are mostly concrete and executable, but there are issues: the Quick Start backend uses the deprecated `paypalrestsdk` library with `Payment.find()` which doesn't align with the v2 Orders API used in the frontend, and the `is_transaction_processed()` function is referenced but never defined. The test example requires manual steps and comments out the critical capture assertion. | 2 / 3 |
Workflow Clarity | While individual API operations are shown, there's no clear end-to-end workflow with validation checkpoints. The payment flow lacks explicit steps like 'verify order status before capture' or 'check HTTP status codes before proceeding.' The IPN handler has duplicate-check logic mentioned but the verification function is incomplete (no error handling for failed verification requests). Missing feedback loops for error recovery in financial operations is a significant gap. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files and no bundle files to support it. All content—Quick Start, Express Checkout, IPN, Subscriptions, Refunds, Error Handling, Testing—is inlined in a single massive file. The subscription and refund sections could easily be separate referenced files, and the PayPalClient class is duplicated conceptually across sections. | 1 / 3 |
Total | 6 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
34632bc
- 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.