Set up self-hosted Inngest on macOS as a durable background task manager for AI agents. Interactive Q&A to match intent — from Docker one-liner to full k8s deployment with persistent state. Use when: 'set up inngest', 'background tasks', 'durable workflows', 'self-host inngest', 'event-driven functions', 'cron jobs', or any request for a local workflow engine.
90
88%
Does it follow best practices?
Impact
94%
2.93xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Worker initialization and dependencies
@inngest/ai installed
0%
100%
hono installed
0%
100%
src/inngest.ts client file
0%
100%
src/serve.ts entry point
0%
100%
src/functions/ directory
0%
100%
EventSchemas type safety
0%
100%
INNGEST_DEV=1 in start command
0%
100%
Port 3111
0%
100%
GET POST PUT on /api/inngest
100%
100%
step.run() wrapping
100%
100%
step.sendEvent() for chaining
100%
100%
Claim-check pattern and concurrency for large data
Claim-check for large output
0%
100%
No large data returned from step
0%
100%
File path passed between steps
0%
100%
GPU concurrency limit
100%
100%
Concurrency key for per-resource limit
100%
100%
step.run() for each discrete step
100%
100%
Function retries configured
100%
100%
Event typing
100%
100%
inngest and @inngest/ai installed
0%
100%
Kubernetes deployment gotchas and service naming
Service not named 'inngest'
0%
100%
StatefulSet used
0%
100%
StatefulSet serviceName matches Service name
0%
100%
Volume mount at /var/lib/inngest
0%
100%
Signing key generation command
50%
100%
signkey-dev- prefix on signing key
0%
0%
evtkey-dev- prefix on event key
0%
0%
inngest start --host 0.0.0.0
0%
100%
Signing keys as env vars
50%
100%
Port 8288 exposed
100%
100%
825972c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.