CtrlK
BlogDocsLog inGet started
Tessl Logo

paypal-integration

Master PayPal payment integration including Express Checkout, IPN handling, recurring billing, and refund workflows.

54

Quality

61%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/paypal-integration/SKILL.md

The canonical home for this skill is paypal-integration in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill is actionable with substantial executable PayPal code, but it is padded with generic boilerplate, lacks sequenced validation checkpoints for destructive payment operations, and references bundle files that are missing while inlining the content that should live in them.

Suggestions

Actually create the referenced bundle files (references/*.md, assets/*.py, resources/implementation-playbook.md) and move the inlined code/catalog content into them, leaving SKILL.md as a concise overview.

Replace the generic "Instructions" and tautological "Do not use this skill when" sections with a concrete end-to-end workflow that includes explicit validation checkpoints (e.g., verify IPN -> check idempotency -> capture -> confirm) for refunds and chargebacks.

Tighten redundant code: the Quick Start capture example duplicates the Express Checkout PayPalClient.capture_order path; keep one and reference the other.

DimensionReasoningScore

Conciseness

The body is mostly code-focused and relevant, but includes padded boilerplate (tautological "Do not use this skill when" bullets, generic "Instructions" like "Apply relevant best practices", and overlapping Quick Start vs. Express Checkout capture code) that could be tightened.

3 / 5

Actionability

Provides concrete, largely executable code for orders, IPN, subscriptions, refunds, and error handling, with minor gaps such as stubbed handlers and undefined helpers like is_transaction_processed.

4 / 5

Workflow Clarity

Content is organized as a code catalog rather than sequenced workflows with validation checkpoints; destructive operations (refunds, chargebacks) lack explicit validate-then-proceed feedback loops, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

A Resources section signals references to references/*.md, assets/*.py and resources/implementation-playbook.md, but those bundle files do not exist, and the corresponding bulk code is inlined in SKILL.md rather than split into the claimed files.

2 / 5

Total

12

/

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.

The description is specific and distinctive, clearly scoping PayPal integration with several concrete sub-capabilities, but it lacks an explicit 'when to use' clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when integrating PayPal checkout, subscriptions, refunds, or IPN webhooks').

Include synonyms like 'subscriptions' and 'webhooks' alongside 'recurring billing' and 'IPN' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete sub-capabilities ("Express Checkout, IPN handling, recurring billing, and refund workflows"), but omits areas like payouts and webhook setup, leaving minor coverage gaps.

4 / 5

Completeness

Provides a clear "what" but no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("PayPal", "Express Checkout", "recurring billing", "refund"), but misses common synonyms such as "subscriptions", "webhooks", and "checkout".

4 / 5

Distinctiveness Conflict Risk

"PayPal payment integration" is a clear, narrowly-scoped niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.