webhook-handler-patterns
Best practices for webhook handlers. Use when implementing the handler sequence (verify first, parse second, handle idempotently), idempotency, error handling, retry logic, or framework-specific issues with Express, Next.js, or FastAPI.
89
89%
Does it follow best practices?
Impact
89%
1.12xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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
Third-party content exposure detected (high risk: 0.80). This skill processes incoming, raw webhook payloads from external providers (e.g., the /webhooks/stripe endpoints shown in references/frameworks/express.md, nextjs.md, fastapi.md and the SKILL.md handler sequence), which are untrusted third-party content that the agent parses and uses to route actions and trigger processing.
- Repository
- hookdeck/webhook-skills
- Commit
daaf3db
- 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.