Download for MacApple silicon, macOS 14+
Skill

inngest-flow-control

@inngest Updated 2026-10-13

Use when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate work from rapid event bursts (debouncing user actions), spreading load over time, ensuring per-tenant fairness, processing events in batches, limiting concurrent runs of the same operation, or assigning priority to important runs. Covers Inngest flow control: concurrency limits with keys, throttling, rate limiting, debounce, priority, singleton, and event batching.

Install

With your agent

Install OMGSkills skill "inngest/inngest-claude-code-plugin:skills/inngest-flow-control" 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-claude-code-plugin /tmp/inngest-claude-code-plugin && ln -s /tmp/inngest-claude-code-plugin/skills/inngest-flow-control ~/.claude/skills/inngest-flow-control

From README

Inngest Flow Control Master Inngest flow control mechanisms to manage resources, prevent overloading systems, and ensure application reliability. This skill covers all flow control options with prescriptive guidance on when and how to use each. 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. Quick Decision Guide "Limit how many run at once" → Concurrency "Spread runs over time" → Throttling "Block after N runs in a period" → Rate Limiting "Wait for activity to stop, then run once" → Debounce "Only one run at a time for this key" → Singleton "Process events in groups" → Batching "Some runs are more important" → Priority Concurrency When to use: Limit the number of executing steps (not function runs) to manage computing resources and prevent system overwhelm. Key insight: Concurrency limits active code execution, not function runs.