メニュー
Update the pinned gemini-live-tools dependency to a PR branch, named branch, version tag, or latest release and verify the installed package.
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.
Launch or restart AlgeBench, open it in Chrome browser tools, and debug UI behavior with console, DOM, screenshots, and interactions.
| name | update-glt |
| description | Update the pinned gemini-live-tools dependency to a PR branch, named branch, version tag, or latest release and verify the installed package. |
| args | [target=<PR_NUMBER|BRANCH_NAME|TAG|latest>] |
Update the gemini-live-tools dependency — either to a PR branch for testing, a specific version tag, or the latest release.
/update-glt [PR_NUMBER | BRANCH_NAME | TAG | "latest"]
Examples:
/update-glt 30 — install from PR #30's branch/update-glt perf/reduce-pcm-buffer-latency — install from a named branch/update-glt v0.1.19 — pin to a specific tag/update-glt latest — upgrade to latest release (same as no argument)/update-glt — upgrade to latest releaseNo argument or "latest": Find the latest tag in gemini-live-tools:
gh api repos/ibenian/gemini-live-tools/releases/latest --jq '.tag_name'
If no releases, find the latest version tag:
git -C /Users/ibenian/dev/gemini-live-tools tag -l 'v*' | sort -V | tail -1
Numeric argument (e.g. 30): Look up the PR branch:
gh pr view <NUMBER> --repo ibenian/gemini-live-tools --json headRefName --jq '.headRefName'
Starts with v + contains dots (e.g. v0.1.19): Use as a version tag directly.
Anything else: Use as a branch name directly.
Replace the gemini-live-tools line in /Users/ibenian/dev/algebench/requirements.txt with:
gemini-live-tools @ git+https://github.com/ibenian/gemini-live-tools.git@<REF>#subdirectory=python
source /Users/ibenian/dev/algebench/.venv/bin/activate && pip install --force-reinstall "gemini-live-tools @ git+https://github.com/ibenian/gemini-live-tools.git@<REF>#subdirectory=python"
source /Users/ibenian/dev/algebench/.venv/bin/activate && python -c "from gemini_live_tools import get_static_content; get_static_content('tts-audio-player.js'); print('OK')"
Tell the user: