creating-webhook-handlers
Create webhook endpoints with signature verification, retry logic, and payload validation. Use when receiving and processing webhook events. Trigger with phrases like "create webhook", "handle webhook events", or "setup webhook handler".
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/api-development/webhook-handler-creator/skills/creating-webhook-handlers/SKILL.mdSecurity
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
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.90). The skill explicitly ingests and processes webhook payloads from public third-party providers (e.g., "ingestion from providers like Stripe, GitHub, Twilio, and Slack" in SKILL.md and the webhook receiver examples in references/examples.md), which are untrusted user-generated inputs that the agent must parse and that can materially influence actions (e.g., triggering deployments, fulfilling orders).
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
Direct money access detected (high risk: 1.00). The skill explicitly targets payment gateways (mentions Stripe and uses stripe.webhooks.constructEvent()) and describes handling payment events like payment_intent.succeeded and charge.refunded to fulfill orders and process refunds. Those are provider-specific payment operations (financial execution-related), not just generic webhook handling. Therefore it qualifies as Direct Financial Execution capability.
- Commit
3a2d27d
- 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.