القائمة
Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | verify |
| description | Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end |
Port 8420 is the user's production backend — never restart or reuse it. Spin up throwaway serve-api instances on spare ports (846x) against isolated project roots instead, and always kill them when done.
Isolated project root: mktemp -d /tmp/obc-verify.XXXXXX, put a minimal
config.toml + empty data/ inside, point OPENBILICLAW_PROJECT_ROOT at it.
data_dir = "data" resolves against that root.
Craft the backend state you need via config/data, not mocks:
api_key (registry build does not call the network at startup).llm_registry_unavailable): all provider keys empty and
launch with env -u OPENAI_API_KEY -u ANTHROPIC_API_KEY -u GOOGLE_API_KEY -u GEMINI_API_KEY — ambient keys silently un-degrade it.data/memory/soul.json into
the tmp root's data/memory/ before launch. is_profile_ready() ==
"soul memory layer has data", loaded at startup (don't hot-drop the file
into a running instance and expect it to flip).Launch (background, stdin must be closed or it hangs):
OPENBILICLAW_PROJECT_ROOT=/tmp/obc-verify.XXX/a \
nohup .venv/bin/openbiliclaw serve-api --host 127.0.0.1 --port 8461 \
> /tmp/obc-verify.XXX/a/server.log 2>&1 < /dev/null &
Ready in ~5-8s. Use the main repo's .venv/bin/openbiliclaw.
Probe with curl --noproxy '*' — the local proxy/TUN hijacks loopback
otherwise. curl -D - for redirect headers, /api/health to confirm the
state you crafted (status, profile_ready), server.log for the
"started in degraded mode" line.
Clean up: kill the PIDs, confirm nothing listens on the ports
(lsof -nP -iTCP:846x -sTCP:LISTEN), rm -rf the tmp roots. Zombie temp
serve-api instances have corrupted real user data before — never skip this.
Use when adding, integrating, hardening, completing, testing, or releasing an OpenBiliClaw platform/source adapter, including anonymous APIs, optional credentials, browser-extension identity or login sources, source-auth/status contracts, discover branches, guided init, config pages, recommendation cards, CLI smoke commands, and real end-to-end validation.
Use when releasing a version, bumping project versions, or pushing release tags.
Use when authoring a spec or implementation plan, or planning multi-task work.
Search for videos on Bilibili using keyword queries generated from user interests.
Use OpenBiliClaw's adapter CLI to sync account signals, read profile summaries, fetch recommendations, submit feedback, and inspect runtime status.
Browse Bilibili pages using agent-browser for visual exploration and DOM interaction.