Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/inngest-brownfield-audit
Use when analyzing an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest. Covers repository discovery, framework and package detection, finding durability gaps in HTTP handlers, webhooks, cron jobs, queues, long-running jobs, AI agents, polling loops, and side-effect-heavy code, then producing and implementing an incremental integration plan.
Passed 15 of 18 test cases with the skill, and 11 of 18 without it.
and 4 more in the full report
6 fixed12 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our existing Next.js app uses an older version of realtime event streaming for durable workflows with @inngest/realtime package installed. During our audit of existing function code, what issue should we flag regarding this import?
| Checked | Without skill | With skill |
|---|---|---|
| The response flags that native v4 realtime imports should be used instead of the legacy @inngest/realtime package. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the user asks Codex to inspect an existing codebase, add Inngest "where it makes sense", migrate fragile background work, or find durability gaps before making changes.
This is an agent-first workflow. Do the audit from evidence in the repo, name the specific files and call sites that drove each conclusion, and make small integration moves that preserve current behavior.
Use this skill for requests like:
If the user is starting from scratch instead of a brownfield repo, use
inngest-setup, inngest-durable-functions, inngest-events,
inngest-steps, and, for AI workflows, the agent patterns in this skill. Use
inngest-agent-evals when the request includes scoring, sessions, experiments,
deferred scorers, Insights, or outcome-based evaluation.
Map the project shape.
package.json, workspace files, app/router structure, server entry
points, deployment config, and test scripts.Find existing Inngest usage.
inngest, createFunction, serve(, /api/inngest,
INNGEST_, step.run, step.sleep, step.waitForEvent,test cases passed, vs 11 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.