メニュー
Recheck an existing normal keypoint evaluation artifact without rerunning the game.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cross-verification |
| description | Recheck an existing normal keypoint evaluation artifact without rerunning the game. |
Use this skill to inspect an existing keypoint artifact directory and write a
fresh recheck_result.json.
Read only:
result.jsontest_result.jsontest_config.jsonDo not rerun Playwright, do not modify original artifacts, and do not inspect unrelated runs.
The output file must contain:
status: PASS, FAIL, or INCOMPLETEpassed: boolean when status is binary, otherwise falseconfidence: integer 0-100reasoning: list of concise evidence bulletsexplanation: complete natural-language explanationconflict_with_original: booleanAnalyze 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.
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.
Orchestrate normal keypoint testing with bounded concurrency.