paddle-webhooks

Receive and verify Paddle webhooks. Use when setting up Paddle webhook handlers, debugging signature verification, or handling subscription events like subscription.created, subscription.canceled, or transaction.completed.

Quality

91%

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

Quality

Content

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

A well-structured, highly actionable skill body with executable verification code and clean one-level references. Its main weaknesses are minor navigational padding and local links to example directories that are not present in the bundle.

Suggestions

Trim the 10-item Related Skills list to the 2-3 most relevant (e.g., webhook-handler-patterns and one payment peer) to reduce navigational token cost in conciseness.

Either add the referenced examples/express, examples/nextjs, and examples/fastapi directories to the bundle or relabel those links as external GitHub pointers so local navigation is not broken, improving progressive_disclosure.

Add a short inline numbered handler workflow (1. verify signature, 2. respond 200, 3. parse, 4. handle idempotently) so the core sequence and its validation checkpoint are explicit rather than delegated, raising workflow_clarity.

Dimension	Reasoning	Score
Conciseness	Core sections (verification code, event table, env var, local dev) are lean and assume Claude's competence, but the 10-entry Related Skills list, Attribution block, and Recommended-skill section are navigational/promotional padding that could be trimmed — efficient with minor over-inclusion rather than fully lean.	4 / 5
Actionability	Copy-paste-ready Node and Python verification functions, the named SDK call paddle.webhooks.unmarshal(...), a concrete env var, and a specific npx hookdeck-cli command fully cover the common cases.	5 / 5
Workflow Clarity	The signature check is an explicit validation gate and the skill is single-purpose, but the full handler sequence (verify → respond 200 → process async → idempotency) is only referenced via examples/ and the recommended patterns skill rather than sequenced inline, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	references/{overview,setup,verification}.md are real, one-level-deep, and clearly signaled, but the body links examples/express/, examples/nextjs/, and examples/fastapi/ which are absent from the bundle — good structure with a minor broken-local-reference gap.	4 / 5
	Total	17 / 20 Passed

Description

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

A strong, third-person description that concretely names capabilities and provides explicit 'Use when' trigger guidance with specific Paddle event types. It is concise, distinct, and comprehensive without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Receive and verify', 'setting up...handlers', 'debugging signature verification', 'handling subscription events' — anchored by specific event names like subscription.created and transaction.completed, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states what ('Receive and verify Paddle webhooks') and when ('Use when setting up... debugging... handling subscription events like...') with concrete trigger phrases, hitting the top anchor.	5 / 5
Trigger Term Quality	Natural user phrases are well covered: 'Paddle webhooks', 'webhook handlers', 'signature verification', 'subscription events', plus concrete event IDs users actually cite, matching the comprehensive natural-terms anchor.	5 / 5
Distinctiveness Conflict Risk	The Paddle-specific niche and named Paddle event types make it clearly distinct from sibling webhook skills (stripe, shopify, etc.), giving minimal conflict risk.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: hookdeck/webhook-skills
Path: skills/paddle-webhooks/SKILL.md
Commit: daaf3db

Reviewed: 3 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.