eval-with-ci

Trigger CI-based benchmark evaluations for the OpenHands software-agent-sdk suite.

3|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/neubig/workflow --skill eval-with-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-with-ci
Source: https://github.com/neubig/workflow/tree/main/skills/eval-with-ci
Command: npx skills add https://github.com/neubig/workflow --skill eval-with-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to automate the execution of CI-based evaluations for the OpenHands/software-agent-sdk, streamlining benchmarking across multiple tools and repos.

Core Features & Use Cases

  • CI-driven evaluation orchestration: triggers and monitors benchmarks like SWE-bench, GAIA, and Terminal-Bench across PRs and workflow runs.
  • Configurable parameters: supports sdk_ref, eval_limit, model_ids, and branch controls to tailor evaluation campaigns.
  • Results routing: automatically dispatches evaluation results to the OpenHands evaluation repositories for review and aggregation.

Quick Start

Trigger a quick evaluation by labeling a PR with run-eval-50 or by dispatching the run-eval workflow.

Frequently Asked Questions about eval-with-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run SWE-bench and GAIA evaluations on a pull request?

You can trigger CI-based SWE-bench and GAIA evaluations on a pull request by applying a specific label like run-eval-50 or by manually dispatching the run-eval workflow within your GitHub Actions pipeline.

Can I configure the evaluation limit and model IDs for GitHub Actions benchmark runs?

Yes, you can parameterize CI-based benchmark runs by configuring eval_limit to control the number of instances evaluated and specifying optional model_ids to target specific models during the workflow dispatch.

What is the best way to automate benchmark evaluations across multiple software agent SDK branches?

The best way to automate benchmark evaluations across SDK branches is to use configurable sdk_ref and branch controls within your CI workflow, dispatching the results automatically to the designated evaluation repository.

Does this CI evaluation workflow support Terminal-Bench alongside SWE-bench?

Yes, the CI-based evaluation orchestration supports triggering and monitoring Terminal-Bench alongside SWE-bench and GAIA benchmarks across pull requests and workflow runs.

How are benchmark evaluation results routed for review after a GitHub Actions run?

Evaluation results are automatically dispatched and routed to the OpenHands evaluation repositories for review and aggregation immediately after the CI-based benchmark workflow completes.

Do I need a specific SDK reference to trigger CI evaluations on a PR?

You can parameterize the sdk_ref to point to a specific software-agent-sdk version or branch, but the workflow also supports default references when triggering evaluations via PR labels or manual dispatch.