Verified:GitHub

webhook-transforms

Convert webhook event payloads into markdown pages with sanitization and dead-letter handling.

5|1|Updated Apr 15, 2026

Search Tags:#knowledge base #webhook #entity extraction #dead-letter queue #data sanitization #markdown transformation #event ingestion

Ready to run

npx skills add https://github.com/GYF0311/lorekit --skill webhook-transforms-gyf0311

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: webhook-transforms
Source: https://github.com/GYF0311/lorekit/tree/main/brain/skills/webhook-transforms
Command: npx skills add https://github.com/GYF0311/lorekit --skill webhook-transforms-gyf0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts messy external webhook payloads (like SMS, meetings, and social mentions) into consistent, safe, brain-ingestible pages so your knowledge base stays up to date automatically.

Core Features & Use Cases

Input-to-page transformation contract: Maps raw JSON payloads to markdown pages with metadata such as slug, type, and citations.
Safety and sanitization guardrails: Strips HTML tags and escapes script content to prevent unsafe data from entering brain pages.
Reliability via dead-letter and retries: Preserves raw payloads and writes failed transforms to a dead-letter queue while retrying once.

Quick Start

Register the webhook endpoint and define the transform mapping so an incoming SMS or meeting event becomes a properly cited brain page with entity extraction and timeline updates.

Frequently Asked Questions about webhook-transforms

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

FAQPage Schema

How do I convert incoming webhook payloads into markdown pages for a knowledge base?▼

Webhook payloads are transformed into markdown pages by mapping raw JSON event data into structured formats with metadata like slugs, types, and citations. This process ensures external event data becomes a consistent, brain-ingestible record for your knowledge base.

What is the best way to sanitize untrusted webhook data before knowledge-base ingestion?▼

Sanitizing untrusted webhook data requires stripping HTML tags and escaping script content to prevent unsafe payloads from entering brain pages. These safety guardrails ensure only clean, secure data is written to your knowledge base.

How do dead-letter queues handle failed webhook event transformations?▼

Dead-letter queues handle failed webhook event transformations by preserving raw payloads and writing failed records to a separate queue while retrying the transform once. This mechanism ensures no data is lost during ingestion failures.

Can I extract entities automatically after writing webhook events to brain pages?▼

Entity extraction occurs automatically after writing webhook events to brain pages. The workflow extracts entities post-page-creation to ensure the structured signal and citation-backed record are fully established before metadata analysis begins.

Does webhook transformation support SMS, meeting, and social mention ingestion workflows?▼

Webhook transformation explicitly supports SMS, meeting, and social mention ingestion workflows. Each event type is mapped from raw JSON payloads into a structured brain signal with timeline updates and citation-backed records.

What steps are needed to automate event ingestion from external webhooks into a brain sync?▼

Automating event ingestion requires registering the webhook endpoint, defining the transform mapping, sanitizing the payload, and completing a brain sync step. This pipeline converts external events into structured brain pages with entity extraction and timeline updates.