paddle-webhooks
Receive and verify Paddle webhooks in a Next.js Route Handler — signature verification, idempotency, retry semantics, and local testing.
72
84%
Does it follow best practices?
Impact
100%
1.20x1 of 3 eval scenarios. Add 2 more for a full score.
Medium
Suggest reviewing before use
The canonical home for this skill is paddle-webhooks in PaddleHQ/paddle-agent-skills
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill documents receiving and verifying webhooks, processing subscription/transaction events in database rows (indirect accounting/syncing), and configuring webhook destinations or calling replay/notification APIs. No direct financial execution (such as initiating payments or transferring funds) is performed or delegated by the agent. Therefore, this is an indirect financial operation.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow processes incoming Paddle webhooks via an HTTP endpoint, which ingests untrusted outsider-submitted free text payloads from webhook notifications.
- Repository
PaddleHQ/paddle-agent-skills
- Revision
70cb70d
- Audited
- Security analysis
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.