verify-outputs

Validate task artifacts against acceptance criteria for existence and non-emptiness.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Void0312Aurora/RAAS --skill verify-outputs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-outputs
Source: https://github.com/Void0312Aurora/RAAS/tree/main/skills/verify-outputs
Command: npx skills add https://github.com/Void0312Aurora/RAAS --skill verify-outputs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Artifacts produced by tasks are often accepted based on presence rather than actual validation. This Skill ensures produced outputs truly satisfy the task requirements and acceptance criteria.

Core Features & Use Cases

  • Verify presence and non-empty status of outputs and logs.
  • Compare artifacts against an acceptance contract or intermediate evidence.
  • Flag and record any mismatches as concrete blockers for task review.
  • Applicable to experiments, reports, and model outputs where rigorous pass/fail judgments are required.

Quick Start

Run verify-outputs after a task completes to validate produced artifacts against the acceptance criteria.

Frequently Asked Questions about verify-outputs

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

FAQPage Schema
How do I validate task outputs against acceptance criteria?

To validate task outputs against acceptance criteria, run the verification process after a task completes to confirm produced artifacts conform to the contract, checking for existence, non-emptiness, and provenance before approval.

What does artifact validation check for in a workflow?

Artifact validation checks for the presence and non-empty status of outputs and logs, compares artifacts against an acceptance contract, and flags any mismatches as concrete blockers for task review.

How do I verify non-empty logs and model outputs in experiments?

You verify non-empty logs and model outputs by running a post-task validation step that enforces rigorous pass or fail judgments based on the existence, non-emptiness, and provenance of the generated artifacts.

Can I flag mismatches in produced artifacts as blockers for review?

Yes, you can flag mismatches in produced artifacts as blockers for review by comparing the generated outputs and logs against an acceptance contract and recording any deviations found during the validation process.

Does artifact verification work for reports and model outputs?

Yes, artifact verification works for reports and model outputs, applying rigorous pass or fail judgments to confirm produced outputs satisfy task requirements and acceptance criteria across experiments and reporting workflows.