eval

Validate brain-os skill eval definitions against SKILL.md content.

16|9|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/sonthanh/brain-os-plugin --skill eval-sonthanh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval
Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/eval
Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill eval-sonthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This evaluation tool ensures that skill edits do not introduce regressions by automatically validating eval definitions across all skills.

Core Features & Use Cases

  • Runs eval checks against brain-os skills to catch regressions
  • Reads evals/evals.json for each skill and validates each entry against its SKILL.md
  • Outputs results in a clear, test-style report suitable for CI workflows

Quick Start

Run /eval to list skills with evals and to execute their checks.

Frequently Asked Questions about eval

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

FAQPage Schema
How do I run regression testing for brain-os skills after making edits?▼

Regression testing for brain-os skills is automated by validating eval definitions against SKILL.md content. Run /eval to list skills with evals and execute their checks, producing a test-style report suitable for CI workflows.

What is skill correctness validation and when do I need it?▼

Skill correctness validation checks that edits to brain-os skills do not introduce regressions. You need it after edits or before releases to verify that each expectation in evals/evals.json matches the content in SKILL.md.

Can I use this eval tool in my CI workflow to catch skill regressions?▼

Yes, the eval tool outputs results in a clear test-style report suitable for CI workflows. It validates eval definitions across all skills in the repository after edits, preventing regressions before releases.

How do I validate eval definitions across all skills in a repository?▼

Validating eval definitions across all skills is done by reading evals/evals.json for each skill and validating each entry against its SKILL.md. Running /eval lists available skills with evals and executes their checks automatically.

What's the best way to prevent regressions when editing SKILL.md files?▼

The best way to prevent regressions when editing SKILL.md files is automated validation of eval definitions. The eval tool reads evals/evals.json for each skill and validates each expectation against the updated SKILL.md content.

Why are my skill edits causing regressions that pass manual review?▼

Skill edits cause regressions because manual review misses expectations defined in evals/evals.json. Automating validation by checking each expectation against SKILL.md content catches regressions that manual review overlooks.