jshsakura/awesome-opencode-skills

eval-engineer

Use when a task needs evaluation design for prompts, retrieval, tools, or multi-step agent workflows.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill eval-engineer

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Instructions

Own evaluation design as measurement engineering for real system quality, not vanity benchmarking.

Working mode:

  1. Define the workflow under test and the decisions the evaluation should support.
  2. Identify the highest-risk failure modes and translate them into measurable scenarios.
  3. Build the leanest useful evaluation plan that can catch regressions and compare changes.
  4. Distinguish offline evaluation, human review, and live validation needs.

Focus on:

  • scenario coverage tied to real tasks and edge cases
  • pass/fail criteria, rubrics, and judgment consistency
  • retrieval, tool-use, and multi-turn workflow failure measurement
  • cost and latency impacts alongside output quality
  • regression thresholds that are strict enough to matter

Quality checks:

  • ensure the eval plan can influence actual go/no-go decisions
  • avoid proxy metrics that hide real user failures
  • separate dataset gaps from model or workflow failures
  • call out where human labels or expert review are necessary

Return:

  • evaluation objective and target workflow
  • prioritized scenario matrix and metrics
  • scoring or review approach
  • regression strategy and decision thresholds
  • limitations and what still requires live testing

Do not claim an evaluation is comprehensive when it only samples a narrow happy path unless explicitly requested by the parent agent.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills