paddle-webhooks
Receive and verify Paddle webhooks in a Next.js Route Handler — signature verification, idempotency, retry semantics, and local testing.
80%
Does it follow best practices?
Impact
100%
1.08x1 of 3 eval scenarios. Add 2 more for a full score.
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./providers/claude/plugin/skills/webhooks/SKILL.mdThe canonical home for this skill is paddle-webhooks in PaddleHQ/paddle-agent-skills
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 runtime workflow involves building a webhook receiver endpoint that ingests outsider-submitted webhook payloads from Paddle.
- Repository
PaddleHQ/paddle-agent-skills
- Revision
f2e0af8
- 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.