菜单
Router/Planner skill for exeris-benchmarks. Produces primary agent, secondary handoffs, execution order, validation gates, and minimal next action for a benchmark task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comparative strict-gate review for exeris-benchmarks. Use on every PR making a cross-target comparative claim — verifies 4 gate artefacts present + `claim-status.json = comparison_eligible` + `track_id` consistent.
Fairness + reproducibility review for exeris-benchmarks. Use on every committed result and every cross-target claim — enforces matched scoping, separation axes, and complete metadata.
Publication-mode scrub review for exeris-benchmarks. Use whenever `publish-report.sh` runs, when an artefact crosses to a publishable surface, or when raw `.jfr` / flamegraph appears.
Router/Planner triage skill for exeris-benchmarks. Classifies task type (architecture / scenario / driver / JMH / target / verification / docs / publication), scope, severity, and recommends primary agent based on primary risk against fairness / reproducibility / strict gate / confidentiality.
TLS comparator label discipline review for exeris-benchmarks. Use on every TLS JMH benchmark / TLS row / TLS report change.
Guard Exeris cross-tier comparisons so Community vs Enterprise claims stay correctly labeled, protocol-consistent, and inference-safe.
| name | exeris-benchmarks-routing-planner |
| description | Router/Planner skill for exeris-benchmarks. Produces primary agent, secondary handoffs, execution order, validation gates, and minimal next action for a benchmark task. |
Given a classified task (see exeris-benchmarks-task-classifier), produce a minimal, risk-aware execution order across exeris-benchmarks-{router,architect,implementer,verification,docs-adr}.
primary_agentsecondary_handoffs (ordered list with reason)execution_plan (3–5 steps)validation_gates (must-pass list)minimal_next_actionSEPARATION_AXIS / COMPARATIVE_GATE → exeris-benchmarks-architect primary; verification secondary.SCENARIO_IMPL / DRIVER_IMPL / JMH_IMPL / TARGET_IMPL → exeris-benchmarks-implementer primary; verification mandatory when result is committed; architect if axis discipline at risk.VERIFICATION → exeris-benchmarks-verification primary; architect if claim shape in scope; docs-adr if methodology amendment needed.DOCS → exeris-benchmarks-docs-adr primary; architect if methodology change crosses cross-repo discipline.PUBLICATION → exeris-benchmarks-architect primary (publication-mode); implementer secondary for the actual publish step.MULTI_DOMAIN → start with architect, list all dominant handoffs.All five contract fields present and gates tied to the specific risk surface.