원클릭으로
eval-routing
[TEST ONLY] Run the next MCP tool routing eval case. NOT for production use.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
[TEST ONLY] Run the next MCP tool routing eval case. NOT for production use.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Preview and audition Wwise sounds using transport objects. Use when the user wants to play, stop, or pause audio in the Wwise authoring tool.
Read-only Wwise project inspection. Use when querying objects, counting, searching, inspecting properties, comparing objects, checking platform linking, or verifying connectivity. Never modifies the project.
Headless Wwise operations via WwiseConsole CLI — create projects, migrate, verify, generate SoundBanks, import, convert external sources, start WAAPI server. Does NOT require WAAPI or Wwise to be running. Use for CI/CD, project creation, or when Wwise is closed.
Configure Switch Containers, Blend Containers, State Groups, randomizers, attenuation curves, and Game Parameter ranges. Use for container-specific and type-specific configuration that goes beyond basic object properties.
Fallback WAAPI passthrough — discover available WAAPI functions, get their schemas, and call any WAAPI function directly. Use ONLY when no specialized wwise-* skill has the right tool.
Global rules and best practices for all Wwise MCP operations. Always load this alongside any other wwise-* skill when working with a Wwise project.
| name | eval-routing |
| description | [TEST ONLY] Run the next MCP tool routing eval case. NOT for production use. |
| user-invocable | true |
This is a TEST/EVAL SKILL ONLY. Do NOT use for production MCP usage. This skill evaluates tool routing decisions one case at a time.
Use /loop to iterate through every test case unattended:
/loop 30s /eval-routing
This invokes /eval-routing every 30 seconds, advancing one case per iteration.
When all cases are tested the skill prints "All cases evaluated", auto-generates the report, and tells you to stop the loop.
Read tests/eval/test_cases.json to get all test cases
Read tests/eval/test_results.json to find which cases have already been tested
Stale-result guard: If ALL cases already have results, auto-reset by running:
python tests/eval/verify.py --check-stale
This will detect stale results (from a prior session) and reset automatically.
Then re-read test_results.json (it will now be empty).
Find the next case (by id) that has no entry in test_results
If all cases are tested:
python tests/eval/report.py to generate the report inlineCronDelete <id>)Clear tests/eval/tool_log.jsonl (write empty string to it)
Now handle the test case prompt as if a real user asked it:
"prompt" field of the test case"cleanup" field in test_cases.jsoncleanup.tool is "set_wwise_object_properties": restore the original value using
set_wwise_object_properties(operations=[{"object": cleanup.object, "properties": {cleanup.property: cleanup.restore_value}}])cleanup.tool is "set_wwise_object_name": rename back using
set_wwise_object_name(object=cleanup.object_after, value=cleanup.restore_name)cleanup.bulk_restore exists: iterate and restore each entry"expected_error": true will have the tool fail at runtime — that's OK.
The eval only checks routing (which tools were called), not whether they succeeded.After fulfilling the prompt, run: python tests/eval/verify.py
Report the result (pass/fail and any tool mismatches).
The progress counter is shown automatically: [PASS] [15/39] Case 15: ...