inngest-api-clilisted
Install: claude install-skill DrOlu/agent-skills
# 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](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 acce