Update to Inngest

{
  "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.",
  "included_files": [
    {
      "relative_path": "references/cli-commands.md",
      "size_in_bytes": 6433
    }
  ],
  "name": "inngest-api-cli",
  "skill_md_contents": "---\nname: inngest-api-cli\ndescription: >-\n  Use when operating Inngest API resources from the terminal with\n  `npx inngest-cli@latest api`: Cloud/local run debugging, event-run lookup,\n  function traces, function invocation, app syncs, webhooks, environments,\n  keys, account checks, and Insights queries. Provides prescriptive command\n  routing for agents: which CLI command to run for a run ID, event ID, app ID,\n  function ID, Cloud environment, API key, missing ID, or potentially mutating\n  operation. Use `inngest-cli` for dev server setup/general CLI workflows and\n  `inngest-api` only when raw REST API v2 docs or OpenAPI fallback are needed.\n---\n\n# Inngest API CLI\n\nFor Cloud operations with connected MCP tools, use `inngest-cloud` first.\nKeep this skill for explicit terminal/HTTP work or a capability missing from\nMCP. Do not ask for an API key when OAuth MCP can complete the task.\n\nUse this skill when the task is operational: inspect, debug, sync, invoke, or\nquery Inngest API resources through the terminal. This skill is intentionally\nprescriptive so agents can act without guessing.\n\nFor general CLI setup, `inngest dev`, Docker, local testing, MCP setup, or\nself-hosted `inngest start`, use `inngest-cli`. For code changes, pair this\nwith the domain skill that owns the code pattern: `inngest-setup`,\n`inngest-durable-functions`, `inngest-events`, `inngest-steps`,\n`inngest-flow-control`, `inngest-realtime`, or `inngest-middleware`.\n\n## First Move\n\nVerify the current CLI surface before relying on memory:\n\n```bash\nnpx inngest-cli@latest api --help\nnpx inngest-cli@latest api <command> --help\n```\n\nThe active API command is `inngest api`. If prompt context or old docs mention\n`inngest alpha api`, switch to `inngest api`.\n\nUse `inngest-api` only when:\n\n- The CLI does not expose the needed endpoint.\n- The user explicitly asks for raw REST API v2.\n- You need the OpenAPI spec or LLM API docs to resolve request shape.\n\nFor complete command flags, read\n[references/cli-commands.md](references/cli-commands.md) after this skill\ntriggers.\n\n## Target Rules\n\n- Local is the default target for `inngest api`.\n- Cloud Production requires `--prod`.\n- Non-production Cloud environments require `INNGEST_ENV=<name>` or `--env`.\n- Prefer `INNGEST_API_KEY` for Cloud API access.\n- Do not pass API keys inline with `--api-key <secret>` unless the user\n  explicitly accepts process-list and transcript exposure.\n- Never write API keys, event keys, signing keys, webhook URLs, or decrypted\n  secrets into source files, docs, fixtures, or final answers.\n\nCommon targets:\n\n```bash\nnpx inngest-cli@latest api health\nnpx inngest-cli@latest api --prod get-account\nINNGEST_ENV=staging npx inngest-cli@latest api --prod get-webhooks\nnpx inngest-cli@latest api --api-host http://127.0.0.1 --api-port 8288 health\n```\n\n## Local Development\n\nFor local app work:\n\n1. Start the user's app with local dev mode when applicable, for example\n   `INNGEST_DEV=1 npm run dev`.\n2. Start the dev server:\n\n   ```bash\n   npx inngest-cli@latest dev\n   ```\n\n3. Prefer Dev Server MCP tools, when available, to list local functions, send\n   test events, inspect runs, and watch status.\n4. Use `npx inngest-cli@latest api ...` for API-compatible local checks,\n   command-help verification, and workflows not exposed through MCP.\n\nIf the local API says the dev server is unavailable, start `inngest dev` or\nswitch to Cloud with `--prod` when the user is debugging deployed runs.\n\n## Command Routing\n\nUse this table before asking the human for more context.\n\n| Situation | Command path |\n| --- | --- |\n| Check CLI/API reachability | `api health` |\n| Confirm Cloud auth | `api --prod get-account` |\n| List environments | `api --prod get-account-envs --limit 10` |\n| List event keys | `api --prod get-account-event-keys --limit 10` |\n| List signing keys | `api --prod get-account-signing-keys --limit 10` |\n| List webhooks | `api --prod get-webhooks` |\n| User gives a run ID | `api --prod get-function-run <run_id>` |\n| Need step-level detail | `api --prod get-function-trace <run_id> --include-output` |\n| User gives an event ID | `api --prod get-event-runs <event_id> --limit 5 --include-output` |\n| Sync a known app ID | `api --prod sync-app --app-id <app_id> --url <serve_url>` |\n| Invoke a known app/function ID | `api --prod invoke-function --app-id <app_id> --function-id <function_id> --data '<json>'` |\n| Discover Insights tables | `api --prod get-insights-tables` |\n| Discover event schemas for Insights | `api --prod get-insights-event-schemas --limit 25` |\n| Draft an Insights query | `api --prod query-insights-prompt --prompt '<request>'` |\n| Run an Insights query | `api --prod query-insights --query '<sql>'` |\n\nIf a command accepts positional IDs, prefer positional IDs in examples because\nthey are shorter and match current help. Flag forms such as `--run-id` are also\naccepted by the current CLI for many path parameters.\n\n## Debug a Run\n\nWhen the user gives a run ID:\n\n```bash\nnpx inngest-cli@latest api --prod get-function-run <run_id>\nnpx inngest-cli@latest api --prod get-function-trace <run_id> --include-output\n```\n\nSummarize status, failed spans, retry state, timing, error names/messages, and\nthe likely code boundary to inspect. Do not paste full traces unless asked.\n\nWhen the user gives an event ID:\n\n```bash\nnpx inngest-cli@latest api --prod get-event-runs <event_id> --limit 5 --include-output\n```\n\nPick the relevant run from the response, then fetch the run and trace. If\nmultiple runs are plausible, explain the candidates and use timestamps,\nfunction IDs, or failure status to choose.\n\n## Missing IDs\n\nDo not immediately ask the user for app IDs, function IDs, or run IDs.\n\nTry, in order:\n\n1. Dev Server MCP tools, if available.\n2. The user's prompt, pasted dashboard URLs, logs, alert text, or stack traces.\n3. Repository config and Inngest serve definitions.\n4. Event ID lookup with `get-event-runs`.\n5. Current CLI help to see if discovery commands such as `get-functions` or\n   `get-app` have appeared.\n\nAsk the user for the ID only after those sources cannot provide it.\n\n## Mutating Operations\n\nRead before write. List or fetch the relevant resource first, then mutate only\nwhen target and intent are clear.\n\nConfirm before running these against Cloud unless the user already specified\nthe account/environment and exact intent:\n\n- `create-env`\n- `patch-env`\n- `create-webhook`\n- `sync-app`\n- `invoke-function`\n- Broad or expensive `query-insights` calls\n\nFor repeatable invocation tests, use a stable idempotency key:\n\n```bash\nnpx inngest-cli@latest api --prod invoke-function \\\n  --app-id <app_id> \\\n  --function-id <function_id> \\\n  --idempotency-key <stable_test_key> \\\n  --data '{\"example\":true}'\n```\n\nFor complex JSON, use `--body-file` to avoid quoting mistakes.\n\n## Insights\n\nUse Insights when the question is analytic, when logs only give partial clues,\nor when the user asks about trends, frequency, volume, failures over time, or\nevent/run data.\n\nStart small:\n\n```bash\nnpx inngest-cli@latest api --prod get-insights-tables\nnpx inngest-cli@latest api --prod get-insights-event-schemas --limit 25\nnpx inngest-cli@latest api --prod query-insights-prompt \\\n  --prompt \"Show failed functions in the last 24 hours\"\n```\n\nInspect generated SQL before running broad queries. Add limits and time windows\nwhen possible.\n\n## Output Handling\n\n- CLI output is JSON. Parse it structurally before making decisions.\n- Use `--raw` only when a downstream command needs exact response bodies.\n- If responses are paginated and `page.hasMore` is true, continue with\n  `--cursor` when complete results are needed.\n- Treat missing `data` on list responses as an empty list unless an error is\n  present.\n- Redact secrets, webhook URLs, token values, and sensitive payload fields in\n  summaries.\n\n## Drift Handling\n\nThe CLI is beta. If behavior differs from this skill:\n\n1. Run top-level and command-specific help.\n2. Check `https://api-docs.inngest.com/llms.txt`.\n3. Check `https://api-docs.inngest.com/api-specs/v2.json`.\n4. Use the `inngest-api` skill for raw REST API fallback.\n\nSome launch material may mention aliases such as `get-run` or\n`invoke-function-by-slug`. Use them only if current `api --help` exposes them.\nIf absent, use `get-function-run` and `invoke-function`.\n"
}