Community生产力与协作github.com

inngest/inngest-steps

用于实现跨进程重启的延迟操作(如24小时购物车放弃提醒、定时跟进),等待人工审批或带超时的外部事件(审核关卡、Webhook回调、异步API完成),在崩溃后无状态丢失地轮询外部服务,调用其他函数并等待结果,对昂贵操作进行记忆化以避免重试时重复执行,或在工作流中并行运行异步任务。涵盖 Inngest 步骤方法:step.run、step.sleep、step.waitForEvent、step.waitForSignal、step.sendEvent、step.invoke、step.ai,以及循环和并行执行模式。

inngest-steps 是什么?

inngest/inngest-steps 技能为开发者提供了一套完整的 Inngest 步骤方法指南,用于在 AI 代理工作流中构建可靠、可恢复且并行化的异步操作。它专注于处理需要持久化状态的关键场景,例如跨进程重启的延迟(如购物车放弃提醒)、带超时的事件等待(如审核审批或 Webhook 回调),以及不会因崩溃丢失状态的轮询。该技能覆盖了核心 Inngest 步骤 API,包括 step.run(执行任意代码)、step.sleep(非阻塞延迟)、step.waitForEvent/step.waitForSignal(等待外部事件或信号)、step.sendEvent(发送事件触发其他工作流)、step.invoke(调用函数并等待结果)和 step.ai(集成 AI 操作)。此外,它还详细说明了循环和并行执行模式,支持开发者高效编排复杂业务流程。该技能适用于任何集成 Inngest 的平台(如 Claude Code、Cursor、Codex 等),帮助开发者避免重复实现错误处理、重试逻辑和状态管理,从而在开发工具和 AI Agent 场景中显著提升工作流可靠性。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/inngest/inngest-skills/tree/main/skills/inngest-steps

Installed? Explore more 生产力与协作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

inngest-steps 是做什么的?

用于实现必须跨进程重启存活的延迟操作(例如,24小时购物车放弃提醒、定时跟进)、等待带超时的人工审批或外部事件(审核关卡、Webhook 回调、异步 API 完成)、在崩溃后无状态丢失地轮询外部服务、调用其他函数并等待其结果、对昂贵操作进行记忆化以避免重试时重复执行,或在工作流中并行运行异步任务。涵盖 Inngest 步骤方法:step.run、step.sleep、step.waitForEvent、step.waitForSignal、step.sendEvent、step.invoke、step.ai,以及循环和并行执行模式。

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

inngest/inngest-durable-functions

Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where they left off. Covers Inngest function configuration, triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability.

inngest/inngest-events

Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.

inngest/inngest-middleware

Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.

inngest/inngest-setup

Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express, Hono, Fastify), connect-as-worker mode, and the local dev server.

相关技能