hook-serve

Manages GitLab CI/CD pipelines for automated testing and deployment workflows.

2|1|Updated Mar 3, 2026

Search Tags:#validation #kafka #webhooks #dlq #ingress #egress #contract-driven

One-click install

npx skills add https://github.com/heyAyushh/hook --skill hook-serve

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: hook-serve
Source: https://github.com/heyAyushh/hook/tree/main
Command: npx skills add https://github.com/heyAyushh/hook --skill hook-serve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openssl, docker, cargo, rustc, firecracker, socat, kcat, and includes scripts (resource) components.

What problem does it solve?

Operators and engineers need a reliable, auditable, and configurable pipeline to receive, validate, normalize, and deliver webhook events without writing custom glue code or risking event loss during downstream outages.

Core Features & Use Cases

Contract-driven configuration: Define ingress, routes, and egress adapters in a single contract.toml and switch behavior by profile.
Durable Kafka backbone: Ingest events into per-source topics, fan-in via relay, and consume from a core topic with replay and DLQ support.
Security and validation: Per-source HMAC validation, strict fail-closed contract validation, payload sanitization, and timestamp/replay protections.
Pluggable adapters and plugins: HTTP/WebSocket/MCP/Kafka adapters with ordered plugins (event_type_alias, require_payload_field, add_meta_flag) for flexible routing and enforcement.
Use case: Run self-hosted webhook ingestion for GitHub and Linear, fan events into Kafka for downstream AI agents, and ensure required deliveries to egress systems with retry and DLQ semantics.

Quick Start

Start the serve runtime with the default-openclaw profile to validate contracts and begin publishing sanitized EventEnvelopes into the Kafka core for downstream relay and smash processing.

Frequently Asked Questions about hook-serve

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

FAQPage Schema

How do I validate and route webhooks reliably using Kafka?▼

You can validate and route webhooks reliably using Kafka by ingesting events into per-source topics, enforcing per-source HMAC signatures, and consuming from a core topic with replayability and dead letter queue support for exhausted deliveries.

What is the best way to handle failed webhook deliveries without losing event data?▼

To handle failed webhook deliveries without losing data, route exhausted deliveries to a dead letter queue (DLQ) while maintaining a durable Kafka backbone that supports event replayability for downstream retry processing.

How do I enforce strict contract validation for ingress webhooks?▼

You enforce strict contract validation by defining ingress routes and egress adapters in a contract.toml file, applying fail-closed validation logic, and executing ordered adapter plugins to sanitize payloads and verify required fields.

Can I use HTTP and WebSocket adapters for Kafka webhook ingestion?▼

Yes, you can use pluggable HTTP, WebSocket, MCP, and external Kafka adapters to ingest webhook events, normalize them into EventEnvelopes, and fan them into a durable Kafka core topic for downstream relay.

Do I need Docker and Firecracker to operate a self-hosted webhook pipeline?▼

Yes, operating this self-hosted webhook pipeline requires Docker, Firecracker, and other dependencies like OpenSSL and kcat to manage the runtime environment and validate Kafka-backed event ingestion.

Why does my webhook pipeline drop events during downstream outages?▼

Webhook pipelines drop events during outages when lacking durable Kafka-backed ingestion; implementing per-source topics with strict fail-closed validation and DLQ handling ensures events survive downstream failures.