inngest/inngest-skills
13 skills17.7k installs351 starsGitHub
Install
npx skills add https://github.com/inngest/inngest-skillsSkills in this repo
1Inngest Eventsinngest-events is an agent skill for designing robust Inngest event payloads, naming conventions, idempotency, fan-out patterns, and system events in TypeScript workflows. It defines the required name and data fields plus optional id, ts, and v schema version properties for every event. Naming guidance enforces domain slash noun dot verb patterns such as billing slash invoice dot paid with past-tense actions and consistent prefixes. Event IDs prevent duplicate processing within a 24-hour deduplication window, with examples tying IDs to invoice, user signup, or order shipment instances. The ts parameter schedules future delivery or preserves chronological ordering across batched sends. Fan-out patterns show one signup event triggering independent welcome email, trial subscription, and CRM sync functions for parallel reliability. System events such as inngest slash function dot failed are documented for failure handling. Developers reach for inngest-events when decoupling services, implementing Stripe-style webhook idempotency, or planning one-trigger many-handler architectures instead of monolithic synchronous handlers.3.1kinstalls2Inngest Durable Functionsinngest-durable-functions is an agent skill for Inngest durable execution in TypeScript covering function creation, triggers, step memoization, idempotency, cancellation, error handling, and observability. The core rule places all non-deterministic code inside step.run because each step re-runs the function from the start while completed steps are memoized. Documented limits are 1,000 steps per function, 4MB per step return, 32MB combined state, and roughly 50-100ms overhead per step HTTP request. createFunction configures unique ids, event triggers with optional if filters, cron schedules with timezones, retries, and concurrency. Idempotency covers producer-side inngest.send custom ids and consumer-side idempotency keys on event fields. Cancellation patterns use cancelOn event matching and timeout cancellation. step.invoke composes smaller functions when limits are hit. Always wrap API calls, database IO, and file operations in steps; keep pure calculations outside. Developers reach for it when webhook handlers drop events, cron jobs are flaky, background jobs fail mid-execution, or workflows must resume after infrastructure crashes with automatic retries.3.1kinstalls3Inngest StepsThe inngest-steps skill covers Inngest step methods for building durable workflows where each step is a separate HTTP request with independent retries. Critical rule: each step re-runs the function from the beginning, so all non-deterministic code must live inside steps, never outside. Documented methods include step.run for retriable work, step.sleep and step.sleepUntil for delays, step.waitForEvent for event matching with timeouts, step.waitForSignal for one-to-one signals, step.sendEvent for fan-out, and step.invoke for calling other functions with typed results. Limits are 1,000 steps and 4MB total step data per function. waitForEvent only catches events sent after the step executes and requires null checks on timeout. waitForSignal uses onConflict replace or fail for pending signals. invoke requires imported function references in v4, not string IDs. Patterns cover loops reusing step IDs with automatic counters and parallel step execution. TypeScript focus is explicit with pointers to Python and Go documentation. Use cases include cart abandonment delays, human approval gates, webhook polling, memoizing expensive operations, and parallel async work inside workflows.3.1kinstalls4Inngest Setupinngest-setup is an Inngest skill for adding durable execution to TypeScript projects covering SDK installation, client configuration, connection modes, and local development. Prerequisites are Node.js 18 plus, TypeScript, and npm, yarn, pnpm, or bun. Step one installs inngest. Step two creates a shared client with a required hyphenated id and documents eventKey, env, isDev, signingKey, baseUrl, logger, and middleware plus typed events via eventType with Zod schemas. Environment variables INNGEST_EVENT_KEY, INNGEST_SIGNING_KEY, INNGEST_DEV, and INNGEST_BASE_URL must not be hardcoded. Critical guidance requires INNGEST_DEV=1 locally because v4 defaults to Cloud mode and missing signing keys cause 500 errors. Step three chooses HTTP serve endpoints for serverless or WebSocket connect for long-running workers. Serve examples cover Next.js App and Pages routers and Express with express.json ten megabyte limit. Connect mode needs Node.js 22.4 plus. Step six starts inngest-cli dev at localhost 8288. Developers reach for it when bootstrapping Inngest, fixing cloud-mode local errors, or choosing serve versus connect patterns.3.1kinstalls5Inngest Middlewareinngest-middleware is an agent skill for cross-cutting concerns on Inngest durable functions through client-level and function-level middleware hooks. It documents structured logging, tracing, Sentry error tracking, payload encryption via @inngest/middleware-encryption, dependency injection with dependencyInjectionMiddleware, custom telemetry, and uniform behavior across many functions. The v4 middleware lifecycle covers onFunctionRun hooks such as beforeExecution, afterExecution, and transformOutput plus onSendEvent transformInput for outbound event payloads. Official packages include encryption middleware with key rotation support and sentryMiddleware requiring Sentry 8 or newer. Custom InngestMiddleware examples show metrics histograms and robust error handling that logs middleware failures without breaking function execution. Best practices require one concern per middleware, graceful error handling, performance awareness, proper typing, and testing with createMockContext and createMockFunction. The skill warns not to install @inngest/realtime on v4 because step.realtime.publish is built in. Developers reach for it when wiring logging, Sentry, encryption, dependency injection,.3kinstalls6Inngest Flow Controlinngest-flow-control is an Inngest-focused skill from inngest/inngest-skills for managing resources in event-driven backends. It covers concurrency limits with keys, throttling, rate limiting, debounce, priority assignment, singleton enforcement, and event batching—patterns needed when external APIs return 429s from OpenAI, HubSpot, or Stripe, when rapid user actions duplicate work, or when per-tenant fairness matters. Developers reach for this skill while implementing Inngest functions that must spread load, cap concurrent runs of the same operation, or prioritize critical jobs over background tasks. The skill maps concrete reliability problems—burst traffic, duplicate events, unfair queueing—to named Inngest primitives instead of ad-hoc sleep-and-retry logic.931installs7Inngest CliInstalls and runs the Inngest CLI and Dev Server for local development, testing, and self-hosted production. A developer uses it to spin up the local Dev Server, debug serve endpoints, or configure a self-hosted Inngest instance.248installs8Inngest RealtimeStreams durable Inngest workflow updates to live UIs using Inngest v4 native realtime channels and topics. A developer uses it for live status pages, AI agent token streaming, log tailing, or human-in-the-loop approval flows.243installs9Inngest ApiInngest-api covers raw REST API v2 usage and reference lookup for endpoints the Inngest CLI does not expose, including auth and OpenAPI discovery. A developer uses it when explicitly needing HTTP, curl, or the Inngest API docs.233installs10Inngest Api CliOperates Inngest API resources from the terminal via `npx inngest-cli@latest api` for run debugging, event-run lookup, function traces, invocation, and app syncs. A developer uses it to inspect, debug, sync, or query Inngest Cloud and local runs without guessing commands.231installs11Inngest AgentsInngest-agents shows how to build durable agents with AgentKit and Inngest step primitives so model and tool calls retry and survive crashes and deploys. A developer uses it for tool-calling agents, human-in-the-loop flows, or realtime agent UIs.164installs12Inngest Brownfield AuditAnalyzes an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest, covering repository discovery and framework/package detection. A developer uses it when adding durable execution to code with polling loops, side-effect-heavy handlers, or long-running jobs.164installs13Inngest V3 V4 MigrationUpgrades an existing TypeScript codebase from Inngest SDK v3 to v4 and fixes mixed v3/v4 API usage. A developer uses it when upgrading Inngest or resolving v3/v4 errors after a partial migration.144installs