inngest-v3-v4-migration
Use when upgrading an existing TypeScript codebase from Inngest SDK v3 to v4, or when fixing mixed v3/v4 API usage. Covers detecting current SDK usage, moving triggers into createFunction options, replacing EventSchemas with eventType/staticSchema, moving serve options to the client, updating realtime imports, rewriting step.invoke string IDs, checkpointing/serverless runtime settings, Connect option changes, and verification.
Install
With your agent
Install OMGSkills skill "inngest/inngest-claude-code-plugin:skills/inngest-v3-v4-migration" 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-claude-code-plugin /tmp/inngest-claude-code-plugin && ln -s /tmp/inngest-claude-code-plugin/skills/inngest-v3-v4-migration ~/.claude/skills/inngest-v3-v4-migration
From README
Inngest v3 to v4 Migration Use this skill when the user asks to upgrade Inngest, fix v3/v4 errors, migrate realtime, or clean up a codebase that has mixed SDK patterns. Primary reference: https://www.inngest.com/docs/reference/typescript/v4/migrations/v3-to-v4 This skill is agent-first: detect actual first, make mechanical API changes in a controlled order, then typecheck and run focused tests. When to Trigger Use this skill for requests like: "Upgrade Inngest from v3 to v4" "Fix our Inngest v4 migration" "We're getting signing key required / cloud mode errors after upgrading" "step.invoke with a string function ID stopped working" "@inngest/realtime broke after installing inngest@4" "Move from EventSchemas to eventType" "Make this existing Inngest repo v4-compatible" If the user asks for a broad codebase reliability audit first, use inngest-brownfield-audit to choose scope, then return here for the v4 changes.
More from this repo
inngest-agents
Used when building durable AI agents or agentic workflows with Inngest and AgentKit, including model calls, tool calls,...
inngest-api
Used when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an...
inngest-api-cli
Used when operating Inngest API resources from the terminal with `npx inngest-cli@latest api`: Cloud/local run...
