output-dev-eval-testing

Skill

Create offline evaluation tests for Output SDK workflows using @outputai/evals. Use when implementing test evaluators with verify(), creating dataset YAML files, building eval workflows, or running workflow tests via CLI.

0Developer Tools

Install

git clone https://github.com/growthxai/output.git ~/.claude/skills/output-dev-eval-testing

What is output-dev-eval-testing?

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

Create and modify files

Declares Write or Edit

~55 tokens of context used while enabled, before you invoke anything

All declared tools (4)

BashEditReadWrite

Documentation

README · ~9 min read

Offline Evaluation Testing

Overview

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)

Reviews

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

Anthropic Example Skills

Public repository for Agent Skills

165.3K stars

agent-development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or

32.8K stars

plugin-structure

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin director