Install any skill in seconds. Free to start, no credit card required.
Get Started Free →growthxai/output-dev-eval-testing
Create offline evaluation tests for Output SDK workflows using @outputai/evals.
Passed 23 of 24 test cases with the skill, and 3 of 24 without it.
and 29 more in the full report
20 fixed3 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 20 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am naming the eval workflow definition file for a workflow named `invoice_parser`. What exact name must be passed to `evalWorkflow({ name: ... })` so the test runner automatically discovers it?
| Checked | Without skill | With skill |
|---|---|---|
| Names the eval workflow invoice_parser_eval. | Missed | Passed |
The instructions your model reads when the skill loads.
The @outputai/evals package provides an offline evaluation framework for testing workflow quality using datasets and evaluators. This is complementary to the runtime evaluator() from @outputai/core:
| Aspect | Runtime Evaluators (@outputai/core) | Offline Eval Tests (@outputai/evals) |
|---|---|---|
| When | During workflow execution | After execution, at test time |
| Where | evaluators.ts in workflow folder | tests/evals/ in workflow folder |
| Purpose | Live quality scoring with confidence | Dataset-driven pass/fail verification |
| Triggered by | Workflow orchestration | output workflow test CLI command |
| Returns | EvaluationBooleanResult, etc. | Verdict helpers (pass/partial/fail) |
Use offline eval testing when you want to validate workflow behavior against known datasets, build regression test suites, or assess subjective quality with LLM judges.
tests/evals/ or tests/datasets/verify() from @outputai/evalsevalWorkflow()output workflow test commandsAdd a tests/ directory inside the workflow folder:
src/workflows/{workflow_name}/
├── workflow.ts
├── steps.ts
├── evaluators.ts # Runtime evaluators (optional)
├── types.ts
└── tests/
├── datasets/
│ ├── happy_path.yml
│ └── edge_case.yml
└── evals/
test cases passed, vs 3 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.