api-quality-check
Check coding-model API quality, capability fit, and drift with LT-lite and B3IT-lite. Use when Codex needs to verify whether an OpenAI/OpenAI-compatible/Anthropic endpoint can support first-token detection, logprob tracking, baseline-vs-current drift checks, or headless API quality smoke tests for coding CLIs, terminal agents, and OpenClaw-style workflows.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/chekhovin/api-quality-checkAPI Quality Check
Use the bundled script to run headless API-quality checks. Treat this skill as script-first: do not recreate LT-lite/B3IT-lite logic inline unless the script is clearly insufficient.
Provider names such as Ark/Volcengine, GLM, DeepSeek, Kimi, SiliconFlow, and similar services are examples only. The primary decision is the endpoint protocol type: OpenAI, OpenAI-Compatible, or Anthropic.
Quick start
Set the path once:
export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
export APIQ="$CODEX_HOME/skills/api-quality-check/scripts/api_quality_check.py"
export APIQ_BATCH="$CODEX_HOME/skills/api-quality-check/scripts/run_batch_checks.sh"
export APIQ_DAILY="$CODEX_HOME/skills/api-quality-check/scripts/run_daily_check.sh"
Run a capability smoke test first:
python "$APIQ" smoke \
--provider "OpenAI-Compatible" \
--base-url "https://ark.cn-beijing.volces.com/api/coding/v3" \
--api-key "$API_KEY" \
--model-id "ark-code-latest" \
--html-output ./smoke.html
For many OpenAI-compatible endpoints, the same command also works if the user pastes the full .../chat/completions URL. The script will normalize it back to the API root automatically.
If you want a ready-to-run provider.json first, generate it with:
python "$APIQ" init-config \
--provider "OpenAI-Compatible" \
--base-url "https://api.siliconflow.cn/v1/chat/completions" \
--api-key "$API_KEY" \
--model-id "deepseek-ai/DeepSeek-V3.2" \
--name "siliconflow-v3-2" \
--config-output ./provider.json
If an endpoint requires client-specific headers, put them in the config JSON as a headers object or pass them with --headers-json. For Kimi coding endpoints, use {"User-Agent":"KimiCLI/2.0.0"} only when the address is under https://api.kimi.com/coding; for the OpenAI-compatible Kimi path, use https://api.kimi.com/coding/v1.
If you already have multiple raw endpoint entries, normalize them into providers.json with:
python "$APIQ" init-batch-config \
--configs ./raw-providers.json \
--config-output ./providers.json
Or run the full batch pipeline:
"$APIQ_BATCH" ./providers.json ./api-quality-out
That command also creates ./api-quality-out/index.html as the landing page for all generated reports.
For one endpoint that you want to check every day and archive by date:
bash "$APIQ_DAILY" ./provider.json ./daily-out my-endpoint
Workflow
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-chekhovin-api-quality-check": {
"enabled": true,
"auto_update": true
}
}
}