← Back to Skills Marketplace
dwhite-oss

Inngest

by dwhite-oss · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
101
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install inngest
Description
Manage Inngest serverless background jobs and event-driven workflows via REST API. Use when asked to send events, trigger functions, list runs, cancel jobs,...
README (SKILL.md)

Inngest Skill

Base event ingestion URL: https://inn.gs/e/\x3CINNGEST_EVENT_KEY> Management API base: https://api.inngest.com/v1

Auth

# Send an event (key in URL)
curl -X POST "https://inn.gs/e/$INNGEST_EVENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"app/user.signup","data":{"userId":"123"}}'

# Management API
curl -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  https://api.inngest.com/v1/runs

Common Operations

Send a single event:

curl -X POST "https://inn.gs/e/$INNGEST_EVENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"app/order.created","data":{"orderId":"ord_123","total":49.99},"user":{"id":"usr_456"}}'

Send a batch of events:

curl -X POST "https://inn.gs/e/$INNGEST_EVENT_KEY" \
  -H "Content-Type: application/json" \
  -d '[{"name":"app/email.sent","data":{"to":"[email protected]"}},{"name":"app/email.sent","data":{"to":"[email protected]"}}]'

List function runs:

curl -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  "https://api.inngest.com/v1/runs?limit=20&status=running"

Get a specific run:

curl -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  "https://api.inngest.com/v1/runs/$RUN_ID"

Cancel a function run:

curl -X DELETE \
  -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  "https://api.inngest.com/v1/runs/$RUN_ID"

List all registered apps:

curl -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  "https://api.inngest.com/v1/apps"

Replay a failed run:

curl -X POST \
  -H "Authorization: Bearer $INNGEST_SIGNING_KEY" \
  "https://api.inngest.com/v1/runs/$RUN_ID/replay"

Tips

  • Event names follow domain/noun.verb convention (e.g. app/user.created)
  • Batch up to 512 events per POST to reduce HTTP overhead
  • The user.id field enables per-user throttle and concurrency controls
  • Filter runs by status (running, completed, failed, cancelled) to keep responses lean
Usage Guidance
This skill appears to be a simple curl-based Inngest helper and is otherwise coherent, but the SKILL.md requires two secrets (INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY) while the registry metadata declares none. Before installing: (1) confirm the platform will let you provide and securely store both env vars; (2) treat INNGEST_SIGNING_KEY as a sensitive secret — only provide it if you trust the skill and platform; (3) verify network calls are limited to inn.gs and api.inngest.com and that you won't accidentally send sensitive data in event payloads; (4) ask the publisher or registry maintainer to update the skill metadata to declare the required env vars and mark the signing key as the primary credential so the platform can surface appropriate warnings and secure storage. If you cannot provide the signing key securely, do not install or run this skill.
Capability Analysis
Type: OpenClaw Skill Name: inngest Version: 1.0.0 The skill bundle provides standard documentation and curl commands for interacting with the official Inngest API (api.inngest.com and inn.gs). It facilitates legitimate background job management and event ingestion using expected environment variables (INNGEST_EVENT_KEY, INNGEST_SIGNING_KEY) without any evidence of malicious intent, data exfiltration, or unauthorized execution.
Capability Assessment
Purpose & Capability
Name/description match the SKILL.md: all examples are REST calls to inn.gs and api.inngest.com for sending events and managing runs. Behavior described in SKILL.md aligns with the stated purpose.
Instruction Scope
Instructions are limited to curl requests against inn.gs and api.inngest.com using two env vars and occasional $RUN_ID. They do not reference other files, system paths, or external endpoints beyond the Inngest domains.
Install Mechanism
This is an instruction-only skill with no install spec and no code files — nothing is written to disk and no external packages are fetched.
Credentials
The SKILL.md explicitly requires INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY (sensitive secrets) but the registry metadata lists no required env vars or primary credential. Either the skill metadata is incomplete (likely) or the platform won't know to prompt for/store these secrets. Requesting signing keys is proportionate for this purpose, but the mismatch is an incoherence risk.
Persistence & Privilege
No special persistence or elevated privileges requested (always:false, no config paths, no modifications to other skills). Autonomous invocation is allowed by default but not combined with other red flags.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install inngest
  3. After installation, invoke the skill by name or use /inngest
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
High-quality API skill by SkillPlexAI
Metadata
Slug inngest
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Inngest?

Manage Inngest serverless background jobs and event-driven workflows via REST API. Use when asked to send events, trigger functions, list runs, cancel jobs,... It is an AI Agent Skill for Claude Code / OpenClaw, with 101 downloads so far.

How do I install Inngest?

Run "/install inngest" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Inngest free?

Yes, Inngest is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Inngest support?

Inngest is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Inngest?

It is built and maintained by dwhite-oss (@dwhite-oss); the current version is v1.0.0.

💬 Comments