Run any Skill in Manus with one click

exeris-benchmarks-task-classifier

Stars0

Forks0

UpdatedJuly 4, 2026 at 09:38

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

exeris-systems

exeris-systems/exeris-benchmarks

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	exeris-benchmarks-task-classifier
description	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.

Exeris Benchmarks Task Classifier

Purpose

Classify incoming work before execution starts. Triage only — no implementation.

Output Contract

Return exactly:

task_class (SEPARATION_AXIS | COMPARATIVE_GATE | SCENARIO_IMPL | DRIVER_IMPL | JMH_IMPL | TARGET_IMPL | VERIFICATION | DOCS | PUBLICATION | MULTI_DOMAIN)
scope (single-scenario | cross-scenario | cross-track | cross-repo)
severity (low | medium | high | critical)
primary_risk
recommended_primary_agent

Classification Heuristics

SEPARATION_AXIS: axis labelling / Community-vs-Enterprise / Pure-vs-Compat / Micro-vs-Runtime / Guard-vs-Exploratory framing.
COMPARATIVE_GATE: comparative claim with strict-gate artefacts; track_id aggregation discipline.
SCENARIO_IMPL: workload definition under scenarios/<name>/.
DRIVER_IMPL: runtime/drivers/ glue, scripts/run-*.sh, launcher-sync.
JMH_IMPL: micro/jmh/ Maven module.
TARGET_IMPL: targets/<app>/ runnable benchmark apps.
VERIFICATION: reproducibility metadata, baseline updates, schema validation, classification enums.
DOCS: benchmark-philosophy / methodology / scenario-catalog / protocol-matrix / TLS matrix / regression-policy / hardware-profiles / instructions.
PUBLICATION: publish-report.sh, publication-mode scrub, cross-repo movement.
MULTI_DOMAIN: at least two classes above are first-order concerns.

Guardrails

Preserve mandatory separation axes.
Preserve comparative strict gate.
Preserve not-a-merge-gate rule.
Preserve enterprise-vs-public scoping.
If uncertain between two classes, emit MULTI_DOMAIN and state both.

Completion Criteria

All five output fields present and each justified in 1-2 concise bullets.

More from this repository

same repository

exeris-benchmarks-comparative-strict-gate-review

exeris-systems/exeris-benchmarks

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.

2026-07-040

exeris-benchmarks-fairness-reproducibility-review

exeris-systems/exeris-benchmarks

Fairness + reproducibility review for exeris-benchmarks. Use on every committed result and every cross-target claim — enforces matched scoping, separation axes, and complete metadata.

2026-07-040

exeris-benchmarks-publication-mode-scrub-review

exeris-systems/exeris-benchmarks

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.

2026-07-040

exeris-benchmarks-routing-planner

exeris-systems/exeris-benchmarks

Router/Planner skill for exeris-benchmarks. Produces primary agent, secondary handoffs, execution order, validation gates, and minimal next action for a benchmark task.

2026-07-040

exeris-benchmarks-tls-label-discipline-review

exeris-systems/exeris-benchmarks

TLS comparator label discipline review for exeris-benchmarks. Use on every TLS JMH benchmark / TLS row / TLS report change.

2026-07-040

exeris-bench-cross-tier-comparison-guard

exeris-systems/exeris-benchmarks

Guard Exeris cross-tier comparisons so Community vs Enterprise claims stay correctly labeled, protocol-consistent, and inference-safe.

2026-03-160

name	exeris-benchmarks-task-classifier
description	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.

Exeris Benchmarks Task Classifier

Purpose

Classify incoming work before execution starts. Triage only — no implementation.

Output Contract

Return exactly:

task_class (SEPARATION_AXIS | COMPARATIVE_GATE | SCENARIO_IMPL | DRIVER_IMPL | JMH_IMPL | TARGET_IMPL | VERIFICATION | DOCS | PUBLICATION | MULTI_DOMAIN)
scope (single-scenario | cross-scenario | cross-track | cross-repo)
severity (low | medium | high | critical)
primary_risk
recommended_primary_agent

Classification Heuristics

SEPARATION_AXIS: axis labelling / Community-vs-Enterprise / Pure-vs-Compat / Micro-vs-Runtime / Guard-vs-Exploratory framing.
COMPARATIVE_GATE: comparative claim with strict-gate artefacts; track_id aggregation discipline.
SCENARIO_IMPL: workload definition under scenarios/<name>/.
DRIVER_IMPL: runtime/drivers/ glue, scripts/run-*.sh, launcher-sync.
JMH_IMPL: micro/jmh/ Maven module.
TARGET_IMPL: targets/<app>/ runnable benchmark apps.
VERIFICATION: reproducibility metadata, baseline updates, schema validation, classification enums.
DOCS: benchmark-philosophy / methodology / scenario-catalog / protocol-matrix / TLS matrix / regression-policy / hardware-profiles / instructions.
PUBLICATION: publish-report.sh, publication-mode scrub, cross-repo movement.
MULTI_DOMAIN: at least two classes above are first-order concerns.

Guardrails

Preserve mandatory separation axes.
Preserve comparative strict gate.
Preserve not-a-merge-gate rule.
Preserve enterprise-vs-public scoping.
If uncertain between two classes, emit MULTI_DOMAIN and state both.

Completion Criteria

All five output fields present and each justified in 1-2 concise bullets.