# Build Durable Inngest Workflows

Background jobs often fail across retries, delays, and service boundaries. This skill guides durable Inngest workflows with reliable steps, events, and controls.

## Install

```bash
npx skillstore add sickn33/inngest
```

## Metadata

- Status: approved
- Slug: sickn33-inngest
- Skillstore revision: r2
- Version status: missing
- Tree hash: 46ca0b3362615e042fc3a9e50e5f765554c987f0d7b918e8f70a81bae093dd8c
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/inngest
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-inngest
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-inngest/manifest

## Capabilities

- Design typed Inngest clients and event schemas.
- Create durable functions with named steps, sleeps, and retries.
- Apply concurrency limits and idempotency to critical workflows.
- Model fan-out, scheduled jobs, webhooks, and long-running pipelines.
- Configure Next.js serve handlers and function registration.
- Review workflows against practical Inngest validation checks.

## Use Cases

- Launch a background job: Create a typed Inngest function and serve route for a new serverless application.
- Harden payment processing: Add durable steps, retries, idempotency, and concurrency controls to payment workflows.
- Design an AI pipeline: Split long document processing into durable, rate-limited steps with stored results.

## Prompt Templates

### Create a starter function

```
Create an Inngest function for [event] in [framework]. Include typed event data, one durable step, and the required serve handler.
```

### Add a scheduled workflow

```
Design an Inngest cron function that runs [schedule], processes [records], limits concurrency, and emits child events for independent work.
```

### Make a webhook durable

```
Refactor my [provider] webhook into an Inngest workflow with signature validation assumptions, idempotency, retries, named steps, and failure handling.
```

### Architect a production pipeline

```
Design a multi-stage Inngest pipeline for [workload]. Specify events, step boundaries, fan-out, concurrency keys, retry policies, timeouts, and observability points.
```

## Limitations

- It does not deploy applications or provision Inngest accounts.
- Examples require adaptation for your framework, SDK version, and data services.
- It does not replace testing against the Inngest development server.
- External services such as Stripe, Resend, and databases need separate configuration.

## Best Practices

- Use stable, descriptive identifiers for every function and step.
- Set idempotency and concurrency controls around payments and limited services.
- Use typed events, bounded retries, and explicit timeouts for maintainable workflows.

## Anti Patterns

- Do not place an entire workflow inside one large step.
- Do not call payment services without a stable idempotency key.
- Do not create unbounded fan-out against rate-limited dependencies.

## Security Audit

- Audited at: 2026-07-24T01:22:57.338\+00:00
- Summary: All 15 static findings are false positives caused by JavaScript interpolation, Markdown fences, framework names, and ordinary application data. No executable shell commands, reconnaissance behavior, prompt injection, or malicious intent were found.

## Stats

- Views: 84
- Downloads: 10
- Favorites: 0
- Popularity score: 0