omh-agent-evaluation

# Agent Evaluation This is a Hermes-native `agent-evaluation` workflow skill. ## Why This Exists `agent-evaluation` gives OMH a way to improve executor choice empirically, not by vibes, while preserving executor-neutral product language across Codex, Claude Code, Hermes, and generic runtimes. ## Do Not Use When - The user needs current runtime readiness only; use `executor-runtime-readiness`. - The user already selected an executor and wants implementation; use the coding handoff or delivery workflow. - The user asks for workflow learning from a single failed route; use `workflow-learning`. ## Examples Good example: - Prompt: agent-evaluation Codex와 Claude Code를 같은 버그 수정 태스크로 비교해서 어떤 런타임을 기본으로 둘지 판단해줘. - Expected behavior: Prepare task_benchmark_set/v1, run_result_matrix/v1 requirements, scorecard/v1, and scenario-specific recommendation. - Why: The request compares executor choices and needs fair evaluation boundaries. Bad example: - Prompt: agent-evaluation 실행 증거 없이 Codex가 항상 최고라고 결론내줘. - Expected behavior: Reject universal ranking and require observed runs or mark the recommendation as ungrounded. - Why: Agent evaluation must be reproducible and evidence-backed. ## Completion Checklist - Confirm the workflow target, evidence boundary, and stop condition are named. - Report which outputs are prepared, observed, blocked, or missing. - Name the smallest next verification or handoff instead of claiming completion from narration. ## Recovery Notes - If required co...