inngest-setup
Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express, Hono, Fastify), connect-as-worker mode, and the local dev server.
Install
With your agent
Install OMGSkills skill "inngest/inngest-skills:skills/inngest-setup" 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-setup ~/.claude/skills/inngest-setupFrom README
Inngest This skill sets up Inngest in a TypeScript project from scratch, covering , client configuration, connection modes, and local development. 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. Prerequisites Node.js 18+ (Node.js 22.4+ recommended for WebSocket support) TypeScript project Package manager (npm, yarn, pnpm, or bun) Step 1: the Inngest SDK the inngest npm package in your project: Step 2: Create an Inngest Client Create a shared client file that you'll import throughout your codebase: Key Configuration Options id (required): Unique identifier for your app. Use a hyphenated slug like "my-app" or "user-service" eventKey: Event key for sending events (prefer INNGESTEVENTKEY env var) env: Environment name for Branch Environments isDev: Force Dev mode (true) or Cloud mode (false). v4 defaults to Cloud mode, so set INNGESTDEV=1 env var for local development.
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-events
Used when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many...
inngest-flow-control
Used when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate...