一键导入
debug-chrome
Launch or restart AlgeBench, open it in Chrome browser tools, and debug UI behavior with console, DOM, screenshots, and interactions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Launch or restart AlgeBench, open it in Chrome browser tools, and debug UI behavior with console, DOM, screenshots, and interactions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactively build a research-grounded mathematical proof or derivation — research the topic on the web (opt-in per source), confirm the derivation path, generate CAS-verified proof JSON via the algebench-proof-anim pipeline, save it under proofs/domains, and open it on the /prove page. Pass --research to stop at a copy-paste research summary + recommended prompt and (optionally) open a pre-filled Derive tab.
Check an AlgeBench lesson for semantic-graph prebaking — validate which baked graphs are still correct, identify which steps need (re)baking, and bake them into the JSON so the server doesn't derive them at request time. Pass `enrich` to also fill node metadata (descriptions, units, dimensions, emoji, domain) in a second LM pass.
Research a mathematical derivation with the user, generate a shareable AlgeBench proof animation JSON, and launch the app to show it rendering. Interactive and AskUserQuestion-driven at every decision point.
Check deployment status and deploy AlgeBench — Render (staging and prod) and the Hugging Face Space (prod mirror). Production is a choose-host (Render/HF/both) and choose-source (current branch/main/staging) flow.
Release workflow for AlgeBench. Reconciles the VERSION file with the prod git tag, tags a new release on main, publishes a GitHub release, then bumps the VERSION file to the next dev version via a PR. Covers version discovery, tag naming conventions, merge checks, and GitHub release creation.
Update the pinned gemini-live-tools dependency to a PR branch, named branch, version tag, or latest release and verify the installed package.
| name | debug-chrome |
| description | Launch or restart AlgeBench, open it in Chrome browser tools, and debug UI behavior with console, DOM, screenshots, and interactions. |
| args | [action=<stop|restart>] |
Launch AlgeBench (if not already running), open it in Chrome via browser tools, and interactively debug the UI.
/debug-chrome [stop|restart]
/debug-chrome — ensure the app is running and open it in Chrome/debug-chrome stop — kill the running server/debug-chrome restart — kill and relaunch the servercurl -s -o /dev/null -w '%{http_code}' http://localhost:8785/
stop, go to step 5.restart, go to step 5 first, then step 2.Run in background:
./algebench scenes/test/test-proof-quadratic.json --debug --server-only &
Wait a few seconds, then verify it's up:
curl -s -o /dev/null -w '%{http_code}' http://localhost:8785/
If still not responding, check if the port is different:
grep 'DEFAULT_PORT' server.py
Adjust the URL accordingly.
Use the Chrome browser tools:
tabs_context_mcp with createIfEmpty: truehttp://localhost:8785Now use Chrome tools (screenshot, javascript_tool, read_console_messages, read_page, etc.) to debug whatever the user needs.
read_console_messages with onlyErrors: truejavascript_tool to query JS variables and DOMcomputer with action: screenshotcomputer with action: left_clickImportant: chat.js variables like activeSpeakBtn, ttsRequestId, ttsPlayer are script-scoped (not ES modules), so they ARE accessible from javascript_tool. If a variable is not accessible, check if it was declared inside a function closure.
Find and kill the process:
lsof -ti :8785 | xargs kill 2>/dev/null || true
Verify it's stopped:
curl -s -o /dev/null -w '%{http_code}' http://localhost:8785/ 2>/dev/null || echo 'stopped'
--debug flag for verbose server logging.