Menu
Orchestrate normal keypoint testing with bounded concurrency.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Analyze game source code and write a concise implementation summary for downstream testing. Use when keypoint verification needs implementation-aware controls, physics, and timing mapping.
Run the full game-gen-eval pipeline in normal mode (state injection + visual interaction verification) from a generated game. Use when you want an end-to-end evaluation that produces summary_report.md and evaluation_report.md.
Recheck an existing normal keypoint evaluation artifact without rerunning the game.
Extract discrete, verifiable, specification-first keypoints from a game description for subsequent evaluation of game logic correctness. Use when preparing `games/{game_name}/keypoints.md` from a description file.
Generate a runnable TypeScript game from a game description file, plus data.md and a state injection API for evaluation. Use when converting `descriptions_example/*.md` into a playable game project under `games/`.
Convert fuzzy keypoint text into concrete short interaction data for executable verification. Use as the normal-mode `keypoint-tester` pre-step, not as a standalone top-level workflow.
| name | keypoint-orchestrator |
| description | Orchestrate normal keypoint testing with bounded concurrency. |
Use this skill when games/{game_name}/keypoints.md exists and a normal
evaluation run must execute one isolated worker per keypoint.
game_namerun_idgame_urlmax_concurrentscreenshot_modescreenshot_intervalEach keypoint worker writes artifacts under:
runs/{game_name}/{run_id}/keypoint_{id}/
Required files per keypoint:
result.jsontest_config.jsontest_script.mjs or test_script.jstest_result.jsonThe orchestrator should collect all completed keypoint results and write:
runs/{game_name}/{run_id}/summary.jsonruns/{game_name}/{run_id}/summary.mdUse the bundled validators:
python3 skills/keypoint-orchestrator/scripts/check_keypoint_count.py \
--keypoints-file "games/${GAME_NAME}/keypoints.md" \
--min-count 30
python3 skills/keypoint-orchestrator/scripts/validate_artifacts.py \
--run-root "runs/${GAME_NAME}/${RUN_ID}" \
--test-mode normal
Validation failure means the run is incomplete and must not be reported as a successful evaluation.