Inngest Middleware
CheckedInngest Middleware streamlines data ingestion by acting as a central hub for various sources, simplifying pipelines and improving reliability.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add inngest/inngest-skills --skill inngest-middleware -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto 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.
Automated safety checks
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
- Scanned
- 3 files, 1,121 lines
About this skill
What it does
The inngest-middleware skill allows you to integrate custom middleware into your Inngest workflows. This enables you to modify or augment data as it flows through your pipelines, providing flexibility for tasks like data transformation, authentication, or logging. It's designed for extending Inngest’s core functionality with your own logic.
When to use it
- Data Transformation: You need to manipulate the data passing through an Inngest workflow before it reaches its final destination (e.g., reformatting dates, converting units).
- Authentication/Authorization: You want to add a layer of authentication or authorization checks within your Inngest pipelines.
- Custom Logging: You require more granular logging than what Inngest provides by default, tailored to your specific needs.
- Enriching Data: Add additional context or information to the data as it moves through the workflow.
Key capabilities
- Integration with Inngest workflows
- Custom middleware implementation
- Data modification within pipelines
- Extensibility of Inngest functionality
Example prompts
- "Add a middleware step to my Inngest pipeline that converts all timestamps to UTC."
- "Implement an authentication check in my Inngest workflow using this middleware."
- “Can you add a middleware function to log the size of each message processed by my Inngest pipeline?”
Tips & gotchas
- Requires familiarity with Inngest concepts and configuration.
- Middleware execution order is important; ensure your logic doesn't interfere with other steps in the workflow.