Skip to content
TrustedSkillsbeta
Back to all skills

Inngest Flow Control

Checked
inngest·vlatest·backend

Manages data ingestion flows within Inngest, ensuring efficient and reliable data movement for streamlined pipelines.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add inngest/inngest-skills --skill inngest-flow-control -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

inngest

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned inngest/inngest-skills at 082798a627.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
082798a627
Manifest
skills/inngest-flow-control/SKILL.md
Scanned
1 file, 311 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The inngest-flow-control skill provides advanced flow control capabilities within inngest workflows. It allows for conditional execution of tasks, looping over data, and handling errors gracefully to create more complex and robust automation pipelines. This skill enables developers to build sophisticated integrations that adapt to varying conditions and data inputs.

When to use it

  • Conditional Task Execution: You need to run certain tasks only when specific criteria are met (e.g., running a deployment task only if tests pass).
  • Data Transformation Loops: You have a list of items requiring the same processing steps, and you want to automate that process iteratively.
  • Error Handling & Retries: You need to implement retry logic or alternative paths based on task failures within your workflow.

Key capabilities

  • Conditional Task Execution (if/else)
  • Looping over data sets
  • Error handling and retries

Example prompts

  • "Run the 'deploy' task only if the 'test' task succeeds."
  • "Iterate through this list of order IDs and process each one with the 'process_order' function."
  • "If the 'send_email' task fails, retry it up to 3 times before proceeding to the 'log_error' task."

Tips & gotchas

The skill requires a working inngest environment. Familiarity with inngest workflow definitions and syntax is necessary to effectively utilize its features.