🦞 GIGO · gigo-lobster-resume: 续跑入口:v2 stable 当前会清理旧 checkpoint 并从头重跑;保留此 slug 作为旧 checkpoint 兼容入口。 Triggers: 继续试吃 / 恢复评测 / resume tasting / continue lobster...
---
name: gigo-lobster-resume
description: "🦞 GIGO · gigo-lobster-resume: 续跑入口:v2 stable 当前会清理旧 checkpoint 并从头重跑;保留此 slug 作为旧 checkpoint 兼容入口。 Triggers: 继续试吃 / 恢复评测 / resume tasting / continue lobster eval."
metadata: {"openclaw":{"emoji":"🦞","os":["darwin","linux","win32"],"requires":{"anyBins":["python3","python","py"]}}}
---
# gigo-lobster-resume
## Mission
- 续跑入口:v2 stable 当前会清理旧 checkpoint 并从头重跑;保留此 slug 作为旧 checkpoint 兼容入口。
- Resume entrypoint: the v2 stable runtime currently clears old checkpoints and starts fresh; this slug remains for legacy checkpoint compatibility.
## Trigger Phrases
- 中文:继续试吃 / 恢复评测 / 继续评估 / 继续龙虾评测
- English: resume tasting / continue lobster eval / resume lobster benchmark / continue tasting
## Execution Rules
1. Use a direct Python command on this skill directory's wrapper file. Never use `cd ... && python ...`; OpenClaw preflight may reject it.
2. Prefer `python3`, then `python`, then `py`.
3. If the user asked in Chinese, append `--lang zh`. If the user asked in English, append `--lang en`.
4. Stream short progress updates while the benchmark is running.
5. Keep stdout/stderr visible and remind the user that the full log is written to `gigo-run.log`.
6. Do not run `--help`, inspect the whole repo, or switch to `main.py` once the wrapper command is clear. Start the wrapper directly.
7. If the wrapper starts a long-running process, do not kill it just because stdout is quiet for a while. A full tasting run often takes 15-25 minutes.
8. While a long run is in progress, monitor the process and tail the log file under `~/.openclaw/workspace/outputs/gigo-lobster-taster/gigo-run.log` instead of improvising a second execution path.
9. Only declare failure if the process exits non-zero, the log shows a traceback, or the user explicitly asks to cancel.
10. Stay attached until the wrapper exits. Do not end the conversation with “I will keep monitoring”; keep polling and only report completion once you have the final score/result files/ref_code (if any).
11. Prefer `process poll` plus `exec tail -n 50 .../gigo-run.log` while monitoring. Do not use a generic full-file `read` on `gigo-run.log`, because the log can be large and may break the chat output.
## Default Behavior
- 中文:默认优先从旧 checkpoint 继续跑,输出目录指向 gigo-lobster-taster。
- English: By default it resumes from the existing checkpoint and writes to the gigo-lobster-taster output directory.
## Recommended Command Shape
```bash
python3 /absolute/path/to/run_resume.py --lang zh
```
If the user explicitly asks for overrides, append the matching CLI flags:
- `--lobster-name "..."` and `--lobster-tags "tag1,tag2"` for a custom lobster persona
- `--output-dir /custom/path` for a custom output directory
- `--require-png-cert` when the user refuses the SVG fallback
- `--skip-upload` or `--register-only` only when the user explicitly asks to change the default upload behavior
## Persona Defaults
- Explicit CLI overrides win first: `--lobster-name` and `--lobster-tags`
- Then read `GIGO_LOBSTER_NAME` and `GIGO_LOBSTER_TAGS`
- Then read `SOUL.md`
- Finally fall back to the default lobster persona
Do not stop for interactive questions unless the user explicitly asks for an interactive run.
don't have the plugin yet? install it then click "run inline in claude" again.