webhooks

Deliver event notifications via HTTP callbacks with HMAC signing and idempotency.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill webhooks-hung-phan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhooks
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/communication/webhooks
Command: npx skills add https://github.com/hung-phan/system-skills --skill webhooks-hung-phan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a secure and efficient way to handle event notifications using HTTP callbacks, eliminating the need for polling and reducing latency.

Core Features & Use Cases

  • Secure Notifications: Delivers events to a controlled endpoint with HMAC signing for verification.
  • Idempotency: Ensures that events are processed once, even if the provider retries sending them.
  • Retry Policy: Implements an exponential backoff strategy to handle transient failures gracefully.
  • Use Case: Ideal for third-party services like Stripe, GitHub, or Shopify to notify your system of events such as payment processing, code changes, or order updates.

Quick Start

Use the /system-review command followed by 'subscribe to webhook events for your service' to set up a webhook notification.

Frequently Asked Questions about webhooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does idempotency work when receiving event notifications via webhooks?

Idempotency ensures HTTP callback events are processed exactly once, even if the provider retries sending them. This prevents duplicate processing of event notifications during transient network failures.

Can I use HMAC signing to verify event notifications from services like Stripe or GitHub?

The best way to handle failed HTTP callbacks is implementing an exponential backoff retry policy. This strategy gracefully manages transient failures when receiving event notifications from third-party services.

Do I need a controlled endpoint to receive webhook event notifications securely?

Yes, HMAC signing verifies event notifications from services like Stripe, GitHub, or Shopify. It authenticates HTTP callbacks delivered to your controlled endpoint for payment processing, code changes, or order updates.

Why use HTTP callbacks instead of polling for system monitoring and automated workflows?

Yes, you need a controlled endpoint to receive webhook event notifications securely. The endpoint receives HMAC-signed HTTP callbacks, ensuring authenticated and reliable delivery of real-time system updates.

Why use HTTP callbacks instead of polling for system monitoring and automated workflows?

HTTP callbacks replace polling for system monitoring and automated workflows by delivering event notifications instantly. This approach significantly reduces latency and network overhead compared to continuously checking for updates.