AGENT SKILL

robustness_benchmark_protocol

Validate clean and shifted robustness benchmark protocols with class-overlap and metric-gap contracts.

License 许可
Apache-2.0
最近更新
2026-09-03
Stars
★ 351
Forks
27

01 前言 Front Matter

name
robustness_benchmark_protocol
description
Validate clean and shifted robustness benchmark protocols with class-overlap and metric-gap contracts.

02 资源文件 2

03 SKILL.md 正文

Robustness Benchmark Protocol

Use this skill when an experiment needs an ImageNet-R-style robustness protocol: a clean control split, a shifted split, a shared label set, and an explicit metric direction. Do not use it to claim full ImageNet reproduction; it only validates benchmark structure and computes gap semantics.

Inputs

  • Clean examples as dictionaries with id, label, and optional features.
  • Shifted examples with the same label vocabulary.
  • Metric name and direction: lower_is_better for error or higher_is_better for accuracy.

Outputs

  • A benchmark specification with clean classes, shifted classes, overlap status, and metric direction.
  • A gap value computed as shifted minus clean for error metrics or clean minus shifted for accuracy metrics.

Workflow

  1. Load or construct clean and shifted example lists.
  2. Verify that the shifted labels are a subset of the clean labels.
  3. Record the shift type and class-overlap evidence.
  4. Compute clean/shifted metric gaps using direction-aware semantics.
  5. Reject protocols that hide class mismatch or metric direction.

Validation

Run python tests/test_protocol.py or validate the tree with the Distiller skill validator.

Limitations

This skill validates protocol mechanics. It does not download ImageNet-R, train models, or certify that a proxy dataset is equivalent to the paper benchmark.

04 同仓库更多 Skills

VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-triton-opt

Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-solve

END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-skill

PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-pattern-fusion

Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-orchestrate

Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-feedback

Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).

★ 351