eval

Run predefined evaluation cases against prompts to validate agent behavior and generate Markdown reports.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/nocoo/deca --skill eval-nocoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval
Source: https://github.com/nocoo/deca/tree/main/skills/eval
Command: npx skills add https://github.com/nocoo/deca --skill eval-nocoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate Deca prompts by running a suite of test cases, collecting results, judging outcomes manually, and generating audit-ready reports to measure alignment with guidelines.

Core Features & Use Cases

  • Run predefined eval cases against prompts (IDENTITY.md, SOUL.md, AGENTS.md) to verify behavior across channels.
  • Generate human-readable Markdown reports and machine-readable JSON outputs for audit trails and collaboration.
  • Support end-to-end workflow: runner.ts executes tests, create pending results, apply judgments, and produce a final Eval Report.

Quick Start

Start the evaluator from the repository root and run the full eval workflow to produce a new report.

Frequently Asked Questions about eval

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

FAQPage Schema
How do I run deterministic prompt evaluation cases against agent prompts?

Deterministic prompt evaluation is performed by executing a predefined suite of test cases against prompts like IDENTITY.md and SOUL.md. The runner validates agent behavior, collects results, and aggregates outcomes into audit-ready reports.

What is the best way to generate audit-ready QA reports for prompt engineering?

Audit-ready QA reports are generated by running evaluation cases against prompts, applying manual judgments to pending results, and producing human-readable Markdown alongside machine-readable JSON outputs for collaboration and audit trails.

How do I validate agent behavior across different channels using prompt testing?

Agent behavior validation is achieved by running predefined evaluation cases against channel-specific prompts such as AGENTS.md. The evaluation workflow executes tests deterministically, aggregates results, and enables manual judging to verify alignment.

Can I use deterministic testing to measure prompt alignment with my guidelines?

Deterministic testing measures prompt alignment by running predefined eval cases against prompts, collecting outcomes, and applying manual judgments. Results are aggregated into final evaluation reports verifying compliance with established guidelines.

What output formats does the prompt evaluation workflow produce for audit trails?

The prompt evaluation workflow produces human-readable Markdown reports for manual review and machine-readable JSON outputs for automated audit trails. These formats support end-to-end collaboration across the testing, judging, and reporting lifecycle.

Why do I need manual judging in a deterministic prompt evaluation workflow?

Manual judging is required in deterministic prompt evaluation to assess pending test results that automated runners cannot validate alone. It enables human oversight of agent behavior outcomes before aggregating final audit-ready reports.