New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Inngest API

by Asymmetric-al in Asymmetric-al/core

A skill your agent uses 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.

AGPL-3.0Auto-check passedBackend & APIs

Install Inngest API

skills CLI
$ npx skills add Asymmetric-al/core --skill inngest-api -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Asymmetric-al/core inngest-api --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/inngest-api .claude/skills/inngest-api && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inngest-api
GitHub stars
381
Token cost
~1.5k tokens
SKILL.md length
694 words
Files
2 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses 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.

  • Works in 4 steps: Confirm whether the request is… → Use inngest-brownfield-audit before… → Follow this upstream guidance under… → …
  • The user explicitly asks for the Inngest REST API v2
  • SKILL.md covers Prefer CLI First, Docs Lookup, Base URLs and Authentication, plus 8 more sections
  • Calls curl and npx; reaches api-docs.inngest.com and api.inngest.com; needs INNGEST_API_KEY

What it does

Inngest API is an agent skill from Asymmetric-al/core. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rest-api-v2.md`).

It sits in Backend & APIs, covering OpenAPI specifications, Technical documentation and REST APIs. It works with OpenAPI. The repository describes itself as: A high-performance, enterprise-grade Next.js 16 application for mission-focused non-profit organizations. Built for high impact teams. The licence is AGPL-3.0.

When your agent uses it

  • The user explicitly asks for the Inngest REST API v2
  • API authentication
  • An endpoint that the Inngest CLI does not expose

Example prompts

  • “/inngest-api”

Requirements

  • Node.js
  • A credential in INNGEST_API_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Confirm whether the request is agent-tooling guidance or product runtime
  2. Use inngest-brownfield-audit before changing existing app workflows or
  3. Follow this upstream guidance under OpenSpec, root AGENTS.md, repo
  4. Keep runtime packages, app code, migrations, and INNGEST_* env

What it can do on your machine

Read from SKILL.md and the folder at commit c30c8ff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api-docs.inngest.com
    • api.inngest.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • INNGEST_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inngest API loads about 1.5k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 694 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Asymmetric-al/core at commit c30c8ff, republished under its AGPL-3.0 licence (© Asymmetric-al). 694 words, ~1,508 tokens.

Download SKILL.mdSave it as .claude/skills/inngest-api/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
inngest-api
description
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.

Inngest REST API v2

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
  • LLM index: https://api-docs.inngest.com/llms.txt
  • OpenAPI v2 spec: https://api-docs.inngest.com/api-specs/v2.json
  • Markdown page pattern: add .md to a docs URL, for example https://api-docs.inngest.com/v2/runs/GetFunctionTrace.md
  • Endpoint request/response schemas: references/rest-api-v2.md

If a Markdown page returns an error or omits generated reference details, use the OpenAPI spec for methods, paths, parameters, request bodies, and schemas.

Base URLs

  • Cloud v2: https://api.inngest.com/v2
  • Local dev server v2: http://localhost:8288/api/v2
  • API docs say the dev server may also be reached through the local server origin. Confirm the actual dev server port before making local requests.

Authentication

The REST API uses Bearer token authentication.

  • Prefer INNGEST_API_KEY for requests from CI, scripts, tools, and agents.
  • Signing keys are primarily for apps communicating with Inngest; use them for API requests only when that is the available, appropriate credential.
  • API keys are for v2 endpoints only.
  • Include X-Inngest-Env or use an environment-scoped API key when operating outside the default production environment.
  • Never paste, print, commit, or log API keys, event keys, signing keys, webhook URLs, or decrypted secrets.

Example:

bash
curl -fsSL \
  -H "Authorization: Bearer $INNGEST_API_KEY" \
  -H "X-Inngest-Env: $INNGEST_ENV" \
  https://api.inngest.com/v2/account

Endpoint Discovery

Use the OpenAPI spec as the source of truth:

bash
curl -fsSL https://api-docs.inngest.com/api-specs/v2.json

Current v2 areas include account, environments, keys, webhooks, apps, function invocation, event-run lookup, function runs, traces, Insights, and partner APIs. Endpoint coverage can change, so inspect the spec before writing a raw request.

For API-only or access-gated endpoints, such as partner-account endpoints, confirm the user has the needed access before attempting a call.

Request Rules

  • Derive method, path, query params, headers, and body from OpenAPI.
  • Do not invent undocumented request fields.
  • Use structured JSON parsing before making decisions from responses.
  • Use body files or here-docs for complex JSON instead of shell-escaped one liners.
  • Add pagination cursors when page.hasMore is true and complete results are needed.
  • Treat missing data in list responses as an empty list unless an error is present.
Show full SKILL.md (265 more words)Show less

Mutation Safety

Read before write. Confirm target account, environment, resource, and intent before raw HTTP mutations unless the user's instruction already makes all of that explicit.

Treat these categories as mutating or side-effecting:

  • Creating or patching environments.
  • Creating webhooks.
  • Syncing apps.
  • Invoking functions.
  • Partner account creation.
  • Broad Insights queries that may be expensive or noisy.

Output Handling

  • Summarize IDs, names, statuses, pagination, and actionable errors.
  • Redact token values, webhook URLs, sensitive payload fields, and decrypted secrets.
  • Do not paste large raw traces, full OpenAPI fragments, or full response bodies unless the user asks.
  • If auth fails, first verify that a credential is present in the environment; then ask the user to provide or rotate INNGEST_API_KEY without pasting it into chat.

This Repository

These upstream Inngest instructions are vendored for agent tooling and integration work in this monorepo.

Repository Triggers

Use this skill when inngest-api matches the current Inngest task. If the right skill is unclear, start with docs/ai/skills/inngest/SKILL.md.

Repository Workflow

  1. Confirm whether the request is agent-tooling guidance or product runtime integration.
  2. Use inngest-brownfield-audit before changing existing app workflows or fragile background work.
  3. Follow this upstream guidance under OpenSpec, root AGENTS.md, repo rulebooks, framework docs, and runtime evidence.
  4. Keep runtime packages, app code, migrations, and INNGEST_* env requirements out of agent-tooling-only changes.

Repository Checklist

  • The task has explicit product-runtime scope before adding Inngest app code or dependencies.
  • Existing workflows were audited before introducing or changing durable workflow behavior.
  • Any MCP usage is backed by a running Inngest dev server on the configured port.
  • Upstream source and license attribution remain documented in docs/ai/skills/inngest/references/upstream.md.

© Asymmetric-al, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/inngest-api of Asymmetric-al/core.

  • SKILL.md
  • references/rest-api-v2.md

Open the folder on GitHubat commit c30c8ff

Compare with similar skills

Inngest API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inngest API compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inngest API this skillAsymmetric-al/core381—~1.5kAutomated safety check: PassAGPL-3.0
Fishjam Platformsoftware-mansion-labs/skills291—~1.7kAutomated safety check: PassMIT
Soundcloud API Integrationsoundcloud/api259—~787Automated safety check: PassNone
API Documenteralirezarezvani/claude-code-tresor777—~1.5kAutomated safety check: PassMIT
OpenAPI Spec Generationwshobson/agents40k9 repos~511Automated safety check: PassMIT
FastAPI ExpertJeffallan/claude-skills12k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Fishjam Platform

    software-mansion-labs/skills

    Fishjam platform fundamentals — domain model and auth shared by all SDKs.

    291 GitHub stars~1.7k tokensUpdated 12 days ago
    Backend & APIsAuto-check passed

  • Soundcloud API Integration

    soundcloud/api

    Integrates applications with the SoundCloud HTTP API using OAuth 2.1, OpenAPI, and developer docs.

    259 GitHub stars~787 tokensUpdated 10 days ago
    Backend & APIsAuto-check passed

  • API Documenter

    alirezarezvani/claude-code-tresor

    Auto-generate API documentation from code and comments. An agent skill from alirezarezvani/claude-code-tresor.

    777 GitHub stars~1.5k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed

  • OpenAPI Spec Generation

    wshobson/agents

    Create, validate and maintain OpenAPI 3.1 specs for REST APIs, whether designed first or generated from existing code, and use them for docs and client SDKs.

    40k GitHub starsUsed in 9 repos~511 tokens
    Backend & APIsAuto-check passed

  • FastAPI Expert

    Jeffallan/claude-skills

    Builds async Python APIs with FastAPI and Pydantic V2, covering endpoints, JWT authentication, async SQLAlchemy, WebSockets and pytest checks against the OpenAPI docs.

    12k GitHub stars~1.8k tokensUpdated 7 days ago
    Backend & APIsAuto-check passed

  • NestJS Expert

    Jeffallan/claude-skills

    Scaffolds NestJS modules, controllers, services, DTOs and guards for TypeScript backends, with validation, JWT and Passport auth, Swagger docs and unit and E2E tests.

    12k GitHub stars~2k tokensUpdated 7 days ago
    Backend & APIsAuto-check passed

More from Asymmetric-al/core

All 43 skills in this repo

  • Idempotency Handling

    Asymmetric-al/core

    Implement idempotency keys and handling to ensure operations can be safely retried without duplicate effects.

    381 GitHub stars~867 tokensUpdated yesterday
    Auto-check passed

  • Accessibility Review

    Asymmetric-al/core

    Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core.

    381 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Email Inbox

    Asymmetric-al/core

    A skill your agent uses when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted…

    381 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check: notes

  • Components Build

    Asymmetric-al/core

    Build modern, composable, and accessible React UI components following the components.build specification.

    381 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Create Agent

    Asymmetric-al/core

    Guides a one-question-at-a-time design interview, captures alignment in agent/EVE-BRIEF.md, then scaffolds and implements a runnable eve agent with verbose teaching comments.

    381 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes

  • Emil Design Engineering

    Asymmetric-al/core

    Design engineering principles and patterns for building polished, accessible web interfaces.

    381 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Inngest API

What does Inngest API do?

A skill your agent uses 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. Inngest API is an agent skill from Asymmetric-al/core. 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.

When should I use Inngest API?

Inngest API fits situations like: the user explicitly asks for the Inngest REST API v2; API authentication; an endpoint that the Inngest CLI does not expose.

How do I install Inngest API in Claude Code?

Run `npx skills add Asymmetric-al/core --skill inngest-api -a claude-code`. Or copy the skill folder (.agents/skills/inngest-api in Asymmetric-al/core) into .claude/skills/inngest-api in your project. Claude Code loads it when a task matches its description.

How do I install Inngest API in Codex?

Run `npx skills add Asymmetric-al/core --skill inngest-api -a codex`. Or copy the skill folder (.agents/skills/inngest-api in Asymmetric-al/core) into .agents/skills/inngest-api in your project. Codex loads it when a task matches its description.

Can I use Inngest API in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Asymmetric-al/core --skill inngest-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inngest-api, .gemini/skills/inngest-api, .github/skills/inngest-api and .opencode/skills/inngest-api in your project.

What does Inngest API need to run?

Going by SKILL.md and its folder, Inngest API needs the command-line tools its instructions call (curl and npx) and credentials named INNGEST_API_KEY. Our summary lists: Node.js; A credential in INNGEST_API_KEY.

Does Inngest API access the network?

SKILL.md names 2 domains. In commands or code: api-docs.inngest.com and api.inngest.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Inngest API safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inngest API use?

Inngest API is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inngest API use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Inngest API?

Skills that share tags, products or a category with Inngest API: Fishjam Platform (software-mansion-labs/skills, 291 stars), Soundcloud API Integration (soundcloud/api, 259 stars), API Documenter (alirezarezvani/claude-code-tresor, 777 stars) and OpenAPI Spec Generation (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inngest API?

Asymmetric-al (a GitHub organization) maintains it in Asymmetric-al/core, which has 381 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 9, 2026.

Source: Asymmetric-al/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.