Agent skill · software engineering · jeremylongshore
lucidchart-webhooks-events
Implement and operate the documented Lucid data-connector webhook lifecycle. Use when a connector needs webhook-assisted source synchronization. Trigger with "Lucid connector webhook".
Why this skill is useful
Adds executable scripts for registering webhooks and handling events from Lucidchart that extend integration capabilities.
What it needs
Requires express installed locally. Requires lucidchart account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lucid Data-Connector Webhook Lifecycle Overview Build webhook-assisted data synchronization only within Lucid's documented data-connector model. Do not claim generic Lucid document, shape, or collaboration event webhooks. Prerequisites A justified Lucid data connector and supported source-system webhook contract Stable source record/event identifiers and reconciliation API Endpoint, identity, retention, observability, replay, and rollback owners Tool Discipline Use Read, Glob, and Grep to inspect connector and handler code, WebFetch for current Lucid and source contracts, and Write or Edit only for local implementation, synthetic fixtures, and redacted receipts. Current Contract Lucid documents a webhook SDK in the context of data connectors. Exact interfaces come from the current SDK/docs. Delivery authentication, signing, event names, ordering, retry, and retention may be source-system responsibilities and must be verified there—not invented as universal Lucid guarantees. Authentication Authenticate each boundary independently: Lucid connector, webhook source, and upstream reconciliation API. Keep secrets server-side; validate the source's documented authenticity mechanism and never invent a LUCIDWEBHOOKSECRET convention. Instructions 1. Prove the use case belongs to a data connector and identify the authoritative source system. 2. Re-fetch Lucid webhook/connector docs and the source's official delivery contract; record unknown guarantees. 3. Define event envelope validation, stable IDs, freshness/replay window, deduplication, ordering tolerance, and reconciliation. 4. Make the receiver acknowledge quickly and enqueue bounded work; isolate poison events and apply backpressure. 5. Treat webhook data as a change hint. Fetch/reconcile authoritative state before mutating connector data when the source contract permits. 6. Test valid, invalid-auth, malformed, duplicate, reordered, delayed, missing-record, partial-sync, and replay scenarios with synthetic fixtures. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-webhooks-events