Agent skill · software engineering · jeremylongshore
groq-webhooks-events
Build event-driven architectures with Groq streaming, batch processing,
Why this skill is useful
Adds executable scripts for real-time SSE streaming and batch processing patterns that aren't in public documentation.
What it needs
Requires groq, groq-sdk installed locally. Requires groq account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Groq Events & Async Patterns Overview Build event-driven architectures around Groq's inference API. Groq does not provide native webhooks, but its sub-second latency enables unique patterns: real-time SSE streaming, batch processing with callbacks, queue-based pipelines, and event processors that use Groq as an LLM classification/extraction engine. This skill uses Read, Write, and Edit to scaffold and update these handlers in your codebase, and curl to exercise the resulting endpoints. Step 1 (the SSE endpoint) is inline below; the batch, webhook-processor, health-monitor, and Python async patterns live in references/implementation.md. Prerequisites groq-sdk (Node) or groq (Python) installed, GROQAPIKEY set Queue system for batch patterns (BullMQ, Redis, SQS) Understanding of Server-Sent Events (SSE) for streaming Authentication Groq authenticates with a single API key. Export GROQAPIKEY in the environment and the SDK reads it automatically — never hard-code the key or embed it in a request body. The key is a bearer credential; treat it like any secret (env var or secrets manager, never committed). No per-request auth headers are needed when the SDK is constructed with new Groq() / AsyncGroq(). Instructions Write each handler as a file in your project (Read/Write/Edit), then drive it with curl to confirm behavior. Step 1: SSE Streaming Endpoint Stream tokens to the browser as they are generated. Set the text/event-stream headers, disable proxy buffering with X-Accel-Buffering: no, and write one data: frame per token, ending with a done event. Steps 2–5: Batch, Webhook Processor, Health Monitor, Python Async The remaining patterns follow the same shape — Groq as a fast inference engine behind a queue or an event loop. Each is documented in full, with runnable code, in references/implementation.md: Step 2 — Batch processing with BullMQ: enqueue prompts, process with a rate-limited worker (concurrency: 5, limiter: 25 RPM), fire a callback per item. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/groq-webhooks-events