inngest-events
Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.
Install
With your agent
Install OMGSkills skill "inngest/inngest-skills:skills/inngest-events" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/inngest/inngest-skills /tmp/inngest-skills && ln -s /tmp/inngest-skills/skills/inngest-events ~/.claude/skills/inngest-eventsFrom README
Inngest Events Master Inngest event design and delivery patterns. Events are the foundation of Inngest - learn to design robust event schemas, implement idempotency, leverage fan-out patterns, and handle system events effectively. These skills are focused on TypeScript. For Python or Go, refer to the Inngest documentation for language-specific guidance. Core concepts apply across all languages.
More from this repo
inngest-durable-functions
Used when building functions that must survive process crashes, retry automatically on failure, run on a schedule,...
inngest-flow-control
Used when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate...
inngest-middleware
Used when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions,...