Skill Evals

Validate Aeon skill outputs against an assertion manifest and detect regressions.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill skill-evals-anajuliabit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Evals
Source: https://github.com/anajuliabit/aeon/tree/main/skills/skill-evals
Command: npx skills add https://github.com/anajuliabit/aeon --skill skill-evals-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Skill Evals catches quality regressions between runs by validating outputs against a per-skill assertion spec, comparing the latest results to the prior eval, and turning new failures into actionable next steps.

Core Features & Use Cases

  • Output validation with assertions: Verifies minimum word counts, required/forbidden patterns, and numeric ranges for each enabled skill output.
  • Regression detection via diff vs prior eval: Classifies outcomes (new fail, fixed, still failing) by comparing today’s checks to the most recent prior eval article.
  • Issue queueing and optional recovery: Files new issues for new failures/quality drops and can resolve issues that were previously detected and later fixed.
  • Operational focus for autonomy: Produces an Action Queue and only notifies when attention is needed (regressions, quality drops, coverage cliffs, or recoveries).

Quick Start

Run Skill Evals for a specific skill by setting var to the skill name, or leave it empty to evaluate every skill listed in evals.json.

Frequently Asked Questions about Skill Evals

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

FAQPage Schema
How do I detect quality regressions in automated agent outputs?

Quality regression detection works by validating outputs against an assertion manifest and comparing the latest run against the prior eval. It classifies outcomes as new fail, fixed, or still failing to pinpoint exactly where output drift occurred.

How do I validate autonomous agent outputs without external network calls?

You can validate agent outputs locally by running coverage audits via scripts against local file inputs. The system checks minimum word counts, required patterns, and numeric ranges, producing a verdict and actionable queue entirely offline.

What is an assertion manifest for output validation?

An assertion manifest is a per-skill specification used to verify output quality. It defines required and forbidden patterns, minimum word counts, and numeric ranges to ensure autonomous operations like daily digests and monitoring logs meet expected standards.

Does Skill Evals work with local file inputs for unattended operations?

Yes, it requires local file inputs including evals.json, aeon.yml, memory/cron-state.json, and prior eval articles. This allows unattended operations like scheduled digests and monitoring logs to be audited offline without external dependencies.

How do I triage issues from failed assertion checks in scheduled monitoring logs?

The system automatically files new issues for new failures or quality drops and can resolve previously detected issues if they are later fixed. It generates an actionable diff-driven queue and only notifies when attention is needed.

What are the limitations of running coverage audits for autonomous agent operations?

Coverage audits are limited to local file inputs and cannot make external network calls. You must have evals.json, aeon.yml, and prior eval articles available locally for the diff-driven comparison and verdict generation to function correctly.