inngest-steps
Use when implementing delays that must survive process restarts (e.g., 24-hour cart abandonment, scheduled follow-ups), waiting for human approval or external events with timeouts (review gates, webhook callbacks, async API completion), polling external services without losing state on crashes, calling other functions and awaiting their results, memoizing expensive operations so they don't re-run on retry, or running async work in parallel inside a workflow. Covers Inngest step methods: step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai, plus patterns for loops and parallel execution.
Install
With your agent
Install OMGSkills skill "inngest/inngest-skills:skills/inngest-steps" 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-skills /tmp/inngest-skills && ln -s /tmp/inngest-skills/skills/inngest-steps ~/.claude/skills/inngest-stepsFrom README
Inngest Steps Build robust, durable workflows with Inngest's step methods. Each step is a separate HTTP request that can be independently retried and monitored. These skills are focused on TypeScript. For Python or Go, refer to the Inngest documentation for language-specific guidance. Core concepts apply across all languages. Core Concept 🔄 Critical: Each step re-runs your function from the beginning. Put ALL non-deterministic code (API calls, DB queries, randomness) inside steps, never outside. 📊 Step Limits: Every function has a maximum of 1,000 steps and 4MB total step data. step.run() Execute retriable code as a step. Each step ID can be reused - Inngest automatically handles counters.
More from this repo
inngest-durable-functions
Used when building functions that must survive process crashes, retry automatically on failure, run on a schedule,...
inngest-events
Used when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many...
inngest-flow-control
Used when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate...