inngest-api SKILL.md skillA
inngest-api from inngest/inngest-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add inngest/inngest-skills/inngest-api@git:20260928.082798aPins git:20260928.082798a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- inngest/inngest-skills
- Path
skills/inngest-api/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260928.082798a, committed Sep 28, 2026
- First version recorded
- Jun 11, 2026
- Size
- 5,045 bytes
- Repository stars
- 29
- License
- a license file GitHub does not identify
Use when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec, Bearer authentication with API keys or signing keys, production and local base URLs, raw curl/fetch requests, request-shape discovery, pagination, secret redaction, and when to prefer the `inngest-api-cli` skill instead.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Inngest REST API v2 For Cloud operations with connected MCP tools, use `inngest-cloud` first. Keep this skill for explicit terminal/HTTP work or a capability missing from MCP. Do not ask for an API key when OAuth MCP can complete the task. Use this skill for raw REST API v2 work and API reference lookup. If the task can be completed through `npx inngest-cli@latest api`, use `inngest-api-cli` instead; the CLI is safer for agents because it handles target/auth flags and endpoint command wiring. ## Prefer CLI First Use `inngest-api-cli` for: - Run and trace debugging from a run ID or event ID. - Account, environment, key, webhook, app sync, and function invocation checks. - Insights table/schema/query workflows. - Local dev server or Cloud operational checks. Use raw REST API v2 only when: - The CLI does not expose the needed endpoint. - The user explicitly asks for HTTP, curl, fetch, OpenAPI, or API docs. - You need to inspect request/response schemas before deciding what to do. ## Docs Lookup When precision matters, fetch current docs instead of guessing: - API overview: `https://api-docs.inngest.com/` - Authentication: `https://api-docs.inngest.com/authentication` …
Read the whole file at its exact version.
How to install
mdr add inngest/inngest-skills/inngest-api@sha256:eb8d30d50992941fThe line at the top of this page pins the label git:20260928.082798a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pha5m2cgg336waiy)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 11, 2026 and Sep 28, 2026, about one every 110 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260928.082798a latest | 2026-09-28 | 082798a | 5,045 B | A | view · diff |
| git:20260611.8a14712 | 2026-06-11 | 8a14712 | 4,824 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5045 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
inngest/inngest-skills · 29 stars · license a license file GitHub does not identify · pushed 2026-09-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pha5m2cgg336waiy GET https://markdownregistry.com/api/v1/resolve?ref=inngest/inngest-skills/inngest-api GET https://markdownregistry.com/api/v1/blob/eb8d30d50992941fcea40259303f15facb2c1876d6a28a64e59c412793151ce0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from inngest/inngest-skills
Every file in inngest/inngest-skills