paddle-webhooks

Receive and verify Paddle webhooks in a Next.js Route Handler — signature verification, idempotency, retry semantics, and local testing.

1.13x

Quality

79%

Does it follow best practices?

Impact

99%

1.13x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

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

Highly actionable, well-sequenced content with strong validation checkpoints and a real feedback loop, plus good progressive disclosure through related-skill and external-doc references. The only weakness is mild repetition of the single-catch rationale across sections.

Suggestions

Consolidate the '401 vs 500 / single catch' rationale into one location and reference it from the others to reduce repetition.

Consider extracting the idempotency-ledger detail into a referenced section so the main flow stays leaner.

Tighten the delivery-contract MCP aside, which is dense and somewhat tangential to the core Route Handler workflow.

Dimension	Reasoning	Score
Conciseness	Generally lean and assumes Claude's competence (no preamble on what webhooks are), but the '401 vs 500 / single catch' rationale is restated across Step 3 commentary, a dedicated paragraph, and Common pitfalls, which is minor padding.	4 / 5
Actionability	Provides copy-paste-ready TypeScript, env vars, an install command, an idempotency ledger with SQL, and concrete verification steps covering the common cases fully.	5 / 5
Workflow Clarity	Steps 1–6 are clearly sequenced with an explicit 'Verify the integration' section and a feedback loop (tamper secret → confirm non-2xx → restore → confirm retry succeeds), satisfying the validation requirement.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep pointers to related skills and external docs; no bundle files exist so the self-contained body is appropriate, though some inline detail could be split out.	4 / 5
	Total	18 / 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.

A strong, specific description that names a clear niche and several concrete capabilities, but it omits an explicit 'Use when...' trigger clause, which limits completeness. Trigger term coverage is good though not exhaustive.

Suggestions

Add an explicit 'Use when...' clause naming the triggering situations (e.g. 'Use when building the server-side endpoint that receives Paddle webhook events').

Expand trigger terms with common synonyms users might say ('Paddle notifications', 'webhook signature', 'Paddle events').

Consider naming file types or SDK cues (e.g. '@paddle/paddle-node-sdk') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Paddle webhooks in a Next.js Route Handler) and lists several concrete capabilities — 'signature verification, idempotency, retry semantics, and local testing' — with only minor coverage gaps.	4 / 5
Completeness	It clearly states what the skill does but the description lacks an explicit 'Use when...' trigger clause; per the guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains natural terms users would say ('Paddle webhooks', 'Next.js', 'signature verification', 'idempotency', 'retry') with good coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is narrow and specific — 'Paddle webhooks in a Next.js Route Handler' — with distinct triggers and minimal risk of overlapping with unrelated skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Path: skills/webhooks/SKILL.md
Commit: de7fcd3

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