Skywork Agent (research/analysis)
OpenAI-compatible client for Skywork AI (api.skywork.ai, APIFree platform). Does a live auth/endpoint probe before any call and reports honestly whether the failure is auth vs server-side.
Setup
- Env:
SKYWORK_API_KEY(present insecrets/env.sh, len 43, prefixsk-sky...). - Optional:
SKYWORK_BASE_URL(defaulthttps://api.skywork.ai/v1),SKYWORK_MODEL. - Python stdlib +
requests.
Usage
bash
. /data/.openclaw/secrets/env.sh
python3 scripts/skywork.py --check # live probe
python3 scripts/skywork.py --list-models # GET /v1/models
python3 scripts/skywork.py --ask "question" # chat/research call
python3 scripts/skywork.py --ask "..." --model Skywork/Skywork-R1
⚠️ Live status (2026-05-31) — endpoint DOWN, not an auth problem
https://api.skywork.ai(Aliyun ALB) returned HTTP 503 "Service Temporarily Unavailable" from the load balancer (<center>alb</center>) on every path (/,/v1/models,/v1/chat/completions,/health), retried 3×.- A 503 from the ALB means the request never reached the application — so the API key could NOT be validated yet. This is a server-side outage on Skywork's side, not a 401/403 auth rejection.
- DNS resolves fine (
alb-...us-east-1.alb.aliyuncsslbintl.com).
Action needed from د. وائل / next steps
1. Retry later — the 503 is transient ALB downtime. Re-runpython3 scripts/skywork.py --check; once it returns OK base=... the key is validated.
2. If it later returns 401/403, the key needs renewal from the Skywork dashboard.
3. Confirm the correct base URL / model id from the Skywork dashboard (the public name Skywork/Skywork-R1 is the assumed default; adjust via SKYWORK_MODEL / --list-models once reachable).The client is built, compiled, and behaves correctly (cleanly separates 503 server-down from auth failure); it just needs a reachable upstream to complete the live auth confirmation.
Live re-check (2026-06-04 23:10)
- After installing/using requests via python3.13, the client runs correctly.
- Upstream still returns HTTP 503 from ALB at https://api.skywork.ai/v1.
- Status remains: wrapper built, endpoint/server unavailable; not an auth failure yet.