菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ls-omniroute-codex |
| description | 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. |
| metadata | {"version":"1.0"} |
| extensions | {"omniroute":{"source_kind":"localsetup-native","local_role":"codex-onboarding","source_repo":"https://github.com/diegosouzapw/OmniRoute","source_ref":"main","source_commit":"0c7f756f922fe3c0408e41852577027b496489bf","package_version":"3.8.43","release_package_commit":"b729a8f27364f072c87082e03bb8e122f3d76251"}} |
Purpose: configure Codex and related agent clients to use OmniRoute safely, with current v3.8.43 setup and launch distinctions.
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" preflight \
--required-access runtime
If OMNIROUTE_API_KEY or OMNIROUTE_BASE_URL is missing, generate durable registration commands:
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" env-commands
Persistent shell files affect future login shells. Already-running terminals, tmux sessions, GUI apps, Codex, OpenCode, and services need a relaunch or service-manager environment update before they inherit new values.
Use this skill for:
~/.codex/<name>.config.toml.wire_api = "responses" for OmniRoute routing./api/cli-tools/codex-settings and /api/cli-tools/codex-profiles checks./v1/models and OmniRoute model metadata.Do not overwrite ~/.codex/config.toml, shell startup files, API keys, provider settings, or model routing rules without explicit user approval. Do not present model_max_output_tokens as effective Codex config when upstream guidance says it is ignored.
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /v1/models --required-access runtime
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /api/cli-tools/codex-settings
python3 "$(python3 _localsetup/tools/localsetup.py --source-root . path package ls-omniroute scripts/omniroute_api.py)" request GET /api/cli-tools/codex-profiles
Use ls-omniroute-proxy for model/provider catalog interpretation and ls-omniroute-admin-automation for persistent server-side configuration changes.
Covers upstream v3.8.43 skills:
config-codex-clicli-setupcli-servePractical 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 context, compression, memory, cache, RTK, and Qdrant configuration workflows. Use for context engineering, prompt compression, memory settings, cache diagnostics, and related safety checks.