Name: paypal
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

paypal

PayPal integration. Manage Accounts. Use when the user wants to interact with PayPal data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/paypal/SKILL.md

Quality

Content

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

The body is highly actionable with executable CLI commands and a useful actions table, and is well structured for navigation. Its main weaknesses are an unnecessary introductory paragraph explaining PayPal and missing validation guidance for the destructive/batch operations it advertises.

Suggestions

Remove or drastically trim the opening paragraph explaining what PayPal is; Claude already knows this and it wastes context tokens.

Add validation/verification checkpoints for destructive and batch actions (e.g., confirm invoice status before delete-invoice, review recipient list before create-batch-payout).

Fix the dangling step references — '1b' appears without a '1a', and 'skip to Step 2' points to a Step 2 that is not labeled — so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("PayPal is a widely used online payment system...") explains what PayPal is — something Claude already knows — and lines like "Use action names and parameters as needed" are filler, fitting the 'mostly efficient but includes some unnecessary explanation' anchor; not severe enough for 2 but not lean enough for 4.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands (login, connection ensure, action list/run, request) plus a Popular actions table give mostly executable guidance with minor gaps (no end-to-end example linking a table actionId to a run command), fitting the 4-anchor better than the fully-covered 5-anchor.	4 / 5
Workflow Clarity	The connect→search→run sequence has state-checking and polling checkpoints, but the skill exposes destructive and batch operations (create-batch-payout, refund-captured-payment, delete-invoice) with no validation/verification steps for them, so the batch/destructive cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are well-organized (Overview, Working with PayPal, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested or buried references and no bundle files to misroute, but the large inlined actions table keeps it just below the ideal 5-anchor split.	4 / 5
	Total	14 / 20 Passed

Description

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

The description successfully states both what the skill does and when to use it, and PayPal is a clearly distinct domain. It is held back by a thin, generic action list (only 'Manage Accounts') and limited trigger-term coverage.

Suggestions

Replace the generic 'Manage Accounts' with 2-3 concrete actions (e.g., 'create and send invoices, manage subscriptions, process payments').

Broaden trigger terms to include natural phrases users say, such as 'payments, invoices, subscriptions, or PayPal transactions'.

Make the 'when' clause more specific by naming the PayPal objects users mention (orders, payouts, refunds) rather than 'interact with PayPal data'.

Dimension	Reasoning	Score
Specificity	The description names the PayPal domain but only offers one minimal, generic action ("Manage Accounts"), matching the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both a 'what' ("PayPal integration. Manage Accounts.") and a 'when' ("Use when the user wants to interact with PayPal data.") are present, but the 'when' could be more specific, matching the 4-anchor rather than the fully concrete 5-anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with PayPal data" includes the natural keyword "PayPal" but misses common variations or synonyms (payments, invoices, send money), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"PayPal integration" is a clear niche with a distinct trigger and minimal conflict risk, though the generic 'interact with PayPal data' phrasing leaves minor overlap with adjacent payment skills, fitting the 4-anchor better than the 5-anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/paypal/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.