인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
개발 및 엔지니어링 · SKILL.md

evaluation_harness_recovery

evaluation_harness_recovery

Use this skill when you need to compose task formatting, model adapter calls, filters, and metrics into an auditable evaluation run.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: evaluation_harness_recovery description: Use this skill when you need to compose task formatting, model adapter calls, filters, and metrics into an auditable evaluation run.

evaluation_harness_recovery

When to use

Use this skill for paper-style language model evaluation harness work where reproducibility depends on explicit task contracts, model-request interfaces, response post-processing, metric aggregation, or an end-to-end auditable run. Do not use it to claim real leaderboard performance without a real model and dataset.

Inputs

  • Small JSON-like task, request, response, or metric records depending on the module.
  • Optional deterministic fake model/data fixtures for bounded validation.
  • A recovery attempt directory when producing experiment evidence.

Outputs

  • Validated Python dictionaries or JSON artifacts with deterministic fields.
  • Clear traces that keep raw responses separate from filtered predictions and scores.

Workflow

  1. Read the task/module contract before executing code.
  2. Validate required fields and fail loudly on incompatible output types or missing metrics.
  3. Preserve raw inputs and produce explicit trace records for downstream modules.
  4. Keep this skill self-contained and avoid reading the original lm-evaluation-harness repository during recovery.
  5. Run the validation command below after edits.

Validation

Run python /share/project/yuyang/workspace/Paper2Skills/Distiller/skills/module-to-skill/scripts/validate_skill_tree.py <skill_dir> --run-tests.

Limitations

These utilities are compact faithful proxies for the harness mechanisms. They are not a replacement for the full upstream package when full-scale benchmark evaluation is required.

Refinement note

Recovery runs should include an explicit source-boundary check showing that the local original repository path is absent from recovery/source_manifest.json.

저장한 Skills