メニュー
OmniRoute observability, usage, quota, resilience, health, policy, audit, and evaluation workflows. Use for monitoring, troubleshooting, cost reports, quota/rate-limit checks, circuit breakers, provider metrics, logs, and non-mutating diagnostics.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Practical Node.js and Next.js project runbook. Use for Node, Next.js, React, package-manager, build, migration, debugging, testing, security, deployment, and version-verification tasks.
Host-first Scrapling integration skill: install or upgrade Scrapling via pipx, run single-URL extractions (simple and structured), and manage adapter and version refresh flows, with Docker as an optional escape hatch.
Project-aware shadcn/ui guide. Use for shadcn setup, components, CLI/MCP, registry, theming, forms, Radix/Base UI, aliases, updates, and troubleshooting in React UI projects.
Use when running a bounded Codex goal loop over GitHub issues, PRs, and maintenance alerts with explicit approval gates.
Comprehensive OmniRoute administration and automation via Python tooling. Use when you need full API-driven control of providers, nodes, aliases, combos, fallbacks, keys, policies, budgets, backup/restore, sync, resilience, and configuration reconciliation with safety gates.
OmniRoute client onboarding and Codex CLI configuration workflow. Use for setup, launch, Codex profile files, wire_api responses configuration, and safe agent-client registration with OmniRoute.
| name | ls-omniroute-observability |
| description | OmniRoute observability, usage, quota, resilience, health, policy, audit, and evaluation workflows. Use for monitoring, troubleshooting, cost reports, quota/rate-limit checks, circuit breakers, provider metrics, logs, and non-mutating diagnostics. |
| metadata | {"version":"1.0"} |
| extensions | {"omniroute":{"source_kind":"localsetup-native","local_role":"observability","source_repo":"https://github.com/diegosouzapw/OmniRoute","source_ref":"main","source_commit":"0c7f756f922fe3c0408e41852577027b496489bf","package_version":"3.8.43","release_package_commit":"b729a8f27364f072c87082e03bb8e122f3d76251"}} |
Purpose: inspect OmniRoute health, usage, quota, cost, resilience, policy, audit, and evaluation state without mutating live configuration.
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" preflight \
--required-access read \
--fail-on-incompatible
Use ls-omniroute first if env vars or access are uncertain. Do not paste keys into commands; use OMNIROUTE_API_KEY or another validated env var name.
Use this skill for:
/api/monitoring/health, provider health, latency, circuit breakers, cooldowns, and resilience checks./api/usage/*, token/cost breakdowns, usage logs, call logs, and analytics./api/quota/*, /api/rate-limit*, budgets, provider quotas, and rate-limit diagnostics./api/compliance/audit-log, policy/audit review, and security event inspection./api/evals and benchmark/evaluation status.Do not use this skill for provider/key mutations, budget writes, or policy changes. Route those to ls-omniroute-admin-automation after explicit approval.
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /api/monitoring/health
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /api/usage/summary
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /api/provider-metrics
If an endpoint is deployment-specific, inspect the current OmniRoute version and route list first rather than guessing. Treat 401/403 as an access mismatch and rerun preflight with the intended access level.
Covers upstream v3.8.43 skills:
omni-budgetomni-usage-logsomni-resiliencecli-cost-usagecli-resiliencecli-healthcli-policy-auditcli-eval