inngest-v3-v4-migration SKILL.md skillA
inngest-v3-v4-migration from asymmetric-al/core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add asymmetric-al/core/inngest-v3-v4-migration@git:20260625.efbcae0Pins git:20260625.efbcae0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- asymmetric-al/core
- Path
.agents/skills/inngest-v3-v4-migration/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260625.efbcae0, committed Jun 25, 2026
- First version recorded
- Jun 25, 2026
- Size
- 11,237 bytes
- Repository stars
- 379
- License
- AGPL-3.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 usage 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. ## Migration Scan Start by locating all Inngest surfaces: ```bash rg -n '"inngest"|"@inngest/realtime"|"@inngest/agent-kit"' package.json **/package.json …
Read the whole file at its exact version.
How to install
mdr add asymmetric-al/core/inngest-v3-v4-migration@sha256:5297dcc1bfc350f3The line at the top of this page pins the label git:20260625.efbcae0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fv443bh4ismw2cxl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Jun 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260625.efbcae0 latest | 2026-06-25 | efbcae0 | 11,237 B | A | view · diff |
| git:20260625.c20d24c | 2026-06-25 | c20d24c | 11,232 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11237 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
asymmetric-al/core · 379 stars · license AGPL-3.0 · pushed 2026-10-22 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_fv443bh4ismw2cxl GET https://markdownregistry.com/api/v1/resolve?ref=asymmetric-al/core/inngest-v3-v4-migration GET https://markdownregistry.com/api/v1/blob/5297dcc1bfc350f3153fa13e2657a0772925f7f5e21f9746bb47e523d1a661d1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from asymmetric-al/core
Every file in asymmetric-al/core