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 CLI

by Asymmetric-al in Asymmetric-al/core

A skill your agent uses when operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging, event-run lookup, function traces, function invocation, app…

AGPL-3.0Auto-check passedBackend & APIs

Install Inngest API CLI

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

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

GitHub CLI
$ gh skill install Asymmetric-al/core inngest-api-cli --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-cli .claude/skills/inngest-api-cli && 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-cli
GitHub stars
381
Token cost
~2.6k tokens
SKILL.md length
1,019 words
Files
2 (incl. references)
Skills in repo
45
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging, event-run lookup, function traces, function invocation, app…

  • Works in 4 steps: Start the user's app with local dev mode… → Start the dev server → Prefer Dev Server MCP tools, when… → …
  • Operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging
  • SKILL.md covers First Move, Target Rules, Local Development and Command Routing, plus 10 more sections
  • Calls npx and npm; reaches api-docs.inngest.com; needs INNGEST_API_KEY

What it does

Inngest API CLI is an agent skill from Asymmetric-al/core. Use when operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging, event-run lookup, function traces, function invocation, app syncs, webhooks, environments, keys, account checks, and Insights queries. Provides prescriptive command routing for agents: which CLI command to run for a run ID, event ID, app ID, function ID, Cloud environment, API key, missing ID, or potentially mutating operation. Use inngest-cli for dev server setup/general CLI workflows and…

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

It sits in Backend & APIs, covering Webhooks, OpenAPI specifications and Linux administration. 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

  • Operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging
  • Event-run lookup
  • Function traces
  • Function invocation

Example prompts

  • “/inngest-api-cli”

Requirements

  • Node.js
  • Docker
  • A credential in INNGEST_API_KEY

Workflow steps

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

  1. Start the user's app with local dev mode when applicable, for example
  2. Start the dev server
  3. Prefer Dev Server MCP tools, when available, to list local functions, send
  4. Use npx inngest-cli@latest api ... for API-compatible local checks,

What it can do on your machine

Read from SKILL.md and the folder at commit 225c02e. 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:

    • npx
    • npm

    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

    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 CLI loads about 2.6k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 152 tokens; SKILL.md has 1,019 words of instructions outside code blocks.

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

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 225c02e, republished under its AGPL-3.0 licence (© Asymmetric-al). 1,019 words, ~2,591 tokens.

Download SKILL.mdSave it as .claude/skills/inngest-api-cli/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
inngest-api-cli
description
Use when operating Inngest API resources from the terminal with `npx inngest-cli@latest api`: Cloud/local run debugging, event-run lookup, function traces, function invocation, app syncs, webhooks, environments, keys, account checks, and Insights queries. Provides prescriptive command routing for agents: which CLI command to run for a run ID, event ID, app ID, function ID, Cloud environment, API key, missing ID, or potentially mutating operation. Use `inngest-cli` for dev server setup/general CLI workflows and `inngest-api` only when raw REST API v2 docs or OpenAPI fallback are needed.

Inngest API CLI

Use this skill when the task is operational: inspect, debug, sync, invoke, or query Inngest API resources through the terminal. This skill is intentionally prescriptive so agents can act without guessing.

For general CLI setup, inngest dev, Docker, local testing, MCP setup, or self-hosted inngest start, use inngest-cli. For code changes, pair this with the domain skill that owns the code pattern: inngest-setup, inngest-durable-functions, inngest-events, inngest-steps, inngest-flow-control, inngest-realtime, or inngest-middleware.

First Move

Verify the current CLI surface before relying on memory:

bash
npx inngest-cli@latest api --help
npx inngest-cli@latest api <command> --help

The active API command is inngest api. If prompt context or old docs mention inngest alpha api, switch to inngest api.

Use inngest-api only when:

  • The CLI does not expose the needed endpoint.
  • The user explicitly asks for raw REST API v2.
  • You need the OpenAPI spec or LLM API docs to resolve request shape.

For complete command flags, read references/cli-commands.md after this skill triggers.

Target Rules

  • Local is the default target for inngest api.
  • Cloud Production requires --prod.
  • Non-production Cloud environments require INNGEST_ENV=<name> or --env.
  • Prefer INNGEST_API_KEY for Cloud API access.
  • Do not pass API keys inline with --api-key <secret> unless the user explicitly accepts process-list and transcript exposure.
  • Never write API keys, event keys, signing keys, webhook URLs, or decrypted secrets into source files, docs, fixtures, or final answers.

Common targets:

bash
npx inngest-cli@latest api health
npx inngest-cli@latest api --prod get-account
INNGEST_ENV=staging npx inngest-cli@latest api --prod get-webhooks
npx inngest-cli@latest api --api-host http://127.0.0.1 --api-port 8288 health

Local Development

For local app work:

  1. Start the user's app with local dev mode when applicable, for example INNGEST_DEV=1 npm run dev.

  2. Start the dev server:

    bash
    npx inngest-cli@latest dev

  3. Prefer Dev Server MCP tools, when available, to list local functions, send test events, inspect runs, and watch status.

  4. Use npx inngest-cli@latest api ... for API-compatible local checks, command-help verification, and workflows not exposed through MCP.

If the local API says the dev server is unavailable, start inngest dev or switch to Cloud with --prod when the user is debugging deployed runs.

Command Routing

Use this table before asking the human for more context.

SituationCommand path
Check CLI/API reachabilityapi health
Confirm Cloud authapi --prod get-account
List environmentsapi --prod get-account-envs --limit 10
List event keysapi --prod get-account-event-keys --limit 10
List signing keysapi --prod get-account-signing-keys --limit 10
List webhooksapi --prod get-webhooks
User gives a run IDapi --prod get-function-run <run_id>
Need step-level detailapi --prod get-function-trace <run_id> --include-output
User gives an event IDapi --prod get-event-runs <event_id> --limit 5 --include-output
Sync a known app IDapi --prod sync-app --app-id <app_id> --url <serve_url>
Invoke a known app/function IDapi --prod invoke-function --app-id <app_id> --function-id <function_id> --data '<json>'
Discover Insights tablesapi --prod get-insights-tables
Discover event schemas for Insightsapi --prod get-insights-event-schemas --limit 25
Draft an Insights queryapi --prod query-insights-prompt --prompt '<request>'
Run an Insights queryapi --prod query-insights --query '<sql>'

If a command accepts positional IDs, prefer positional IDs in examples because they are shorter and match current help. Flag forms such as --run-id are also accepted by the current CLI for many path parameters.

Debug a Run

When the user gives a run ID:

bash
npx inngest-cli@latest api --prod get-function-run <run_id>
npx inngest-cli@latest api --prod get-function-trace <run_id> --include-output

Summarize status, failed spans, retry state, timing, error names/messages, and the likely code boundary to inspect. Do not paste full traces unless asked.

When the user gives an event ID:

bash
npx inngest-cli@latest api --prod get-event-runs <event_id> --limit 5 --include-output

Pick the relevant run from the response, then fetch the run and trace. If multiple runs are plausible, explain the candidates and use timestamps, function IDs, or failure status to choose.

Missing IDs

Do not immediately ask the user for app IDs, function IDs, or run IDs.

Try, in order:

  1. Dev Server MCP tools, if available.
  2. The user's prompt, pasted dashboard URLs, logs, alert text, or stack traces.
  3. Repository config and Inngest serve definitions.
  4. Event ID lookup with get-event-runs.
  5. Current CLI help to see if discovery commands such as get-functions or get-app have appeared.

Ask the user for the ID only after those sources cannot provide it.

Show full SKILL.md (381 more words)Show less

Mutating Operations

Read before write. List or fetch the relevant resource first, then mutate only when target and intent are clear.

Confirm before running these against Cloud unless the user already specified the account/environment and exact intent:

  • create-env
  • patch-env
  • create-webhook
  • sync-app
  • invoke-function
  • Broad or expensive query-insights calls

For repeatable invocation tests, use a stable idempotency key:

bash
npx inngest-cli@latest api --prod invoke-function \
  --app-id <app_id> \
  --function-id <function_id> \
  --idempotency-key <stable_test_key> \
  --data '{"example":true}'

For complex JSON, use --body-file to avoid quoting mistakes.

Insights

Use Insights when the question is analytic, when logs only give partial clues, or when the user asks about trends, frequency, volume, failures over time, or event/run data.

Start small:

bash
npx inngest-cli@latest api --prod get-insights-tables
npx inngest-cli@latest api --prod get-insights-event-schemas --limit 25
npx inngest-cli@latest api --prod query-insights-prompt \
  --prompt "Show failed functions in the last 24 hours"

Inspect generated SQL before running broad queries. Add limits and time windows when possible.

Output Handling

  • CLI output is JSON. Parse it structurally before making decisions.
  • Use --raw only when a downstream command needs exact response bodies.
  • If responses are paginated and page.hasMore is true, continue with --cursor when complete results are needed.
  • Treat missing data on list responses as an empty list unless an error is present.
  • Redact secrets, webhook URLs, token values, and sensitive payload fields in summaries.

Drift Handling

The CLI is beta. If behavior differs from this skill:

  1. Run top-level and command-specific help.
  2. Check https://api-docs.inngest.com/llms.txt.
  3. Check https://api-docs.inngest.com/api-specs/v2.json.
  4. Use the inngest-api skill for raw REST API fallback.

Some launch material may mention aliases such as get-run or invoke-function-by-slug. Use them only if current api --help exposes them. If absent, use get-function-run and invoke-function.

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-cli 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-cli of Asymmetric-al/core.

  • SKILL.md
  • references/cli-commands.md

Open the folder on GitHubat commit 225c02e

Compare with similar skills

Inngest API CLI 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 CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inngest API CLI this skillAsymmetric-al/core381—~2.6kAutomated safety check: PassAGPL-3.0
Fishjam Platformsoftware-mansion-labs/skills291—~1.7kAutomated safety check: PassMIT
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT
Old Coder API DesignAmazingAng/old-coder749—~3.4kAutomated 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 11 days ago
    Backend & APIsAuto-check passed

  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed

  • Old Coder API Design

    AmazingAng/old-coder

    Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.

    749 GitHub stars~3.4k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • API Caller

    NVIDIA/SkillEvaluator

    Official

    Call any REST API dynamically. An agent skill from NVIDIA/SkillEvaluator.

    552 GitHub stars~1.1k tokensUpdated today
    Backend & APIsAuto-check passed

More from Asymmetric-al/core

All 45 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 today
    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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed

Works with

Categories

Questions about Inngest API CLI

What does Inngest API CLI do?

A skill your agent uses when operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging, event-run lookup, function traces, function invocation, app…. Inngest API CLI is an agent skill from Asymmetric-al/core. Use when operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging, event-run lookup, function traces, function invocation, app syncs, webhooks, environments, keys, account checks, and Insights queries.

When should I use Inngest API CLI?

Inngest API CLI fits situations like: operating Inngest API resources from the terminal with npx inngest-cli@latest api: Cloud/local run debugging; event-run lookup; function traces; function invocation.

How do I install Inngest API CLI in Claude Code?

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

How do I install Inngest API CLI in Codex?

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

Can I use Inngest API CLI 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-cli -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-cli, .gemini/skills/inngest-api-cli, .github/skills/inngest-api-cli and .opencode/skills/inngest-api-cli in your project.

What does Inngest API CLI need to run?

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

Does Inngest API CLI access the network?

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

Is Inngest API CLI 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 CLI use?

Inngest API CLI 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 CLI use?

About 2.6k tokens (SKILL.md is roughly 10k 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 CLI?

Skills that share tags, products or a category with Inngest API CLI: Fishjam Platform (software-mansion-labs/skills, 291 stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars), Use Yaak (mountain-loop/yaak, 19k stars) and API Designer (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inngest API CLI?

Asymmetric-al (a GitHub organization) maintains it in Asymmetric-al/core, which has 381 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 8, 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.