← ClaudeAtlas

codex-radar-providerlisted

Consume locally consented or officially authorized Codex Radar observations through the host provider CLI for model-aware scheduling, with SQLite-backed offline last-known-good snapshots and explicit freshness boundaries.
lisihao/codex-workbench · ★ 2 · Code & Development · score 58
Install: claude install-skill lisihao/codex-workbench
# Codex Radar Provider Use this Skill when Workbench or DSH needs Codex Radar model-quality, cost, runtime, or other benchmark observations for scheduling and capability calibration. ## Provider CLI Use the host-provided `codex-radar-provider` command for collection and reads, for example: ```text codex-radar-provider --state-root <DIR> consent --personal-use codex-radar-provider --state-root <DIR> status codex-radar-provider --state-root <DIR> show [--snapshot-id <ID>] codex-radar-provider --state-root <DIR> refresh --authorization-file <RECEIPT> codex-radar-provider --state-root <DIR> import --authorization-file <RECEIPT> --payload-dir <DIR> ``` The repository's portable Python package implements this host contract; this Skill does not start it automatically. The Provider's `<state_root>/radar.sqlite3` is the authoritative store for snapshots, raw payloads, models, insights, and the active pointer. JSON files under `raw/`, `generations/`, and `active.json` are compatibility projections only; a valid legacy projection is automatically migrated into SQLite on first read. Prefer a scheduled refresh at most once per 86400 seconds when online, and use `status`/`show` for offline reads. Preserve the returned `schema_version`, `snapshot_id`, `digest`, timestamps, authorization/consent, cache state, source URLs, and model observations in consumer provenance. `status` exposes the database descriptor `{backend, schema_version, path, row_counts}`. Treat `radar.sqlite3` as the so