orch-eval

Evaluate autonomous agent run infrastructure health against a ten-dimension rubric.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill orch-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orch-eval
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/orch-eval
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill orch-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the difficulty of auditing autonomous agent runs by providing a standardized, evidence-based framework to evaluate infrastructure health and operational performance.

Core Features & Use Cases

  • Infrastructure Auditing: Grades agent runs across ten dimensions (O1-O10) including resource release, memory pressure, and slot citizenship.
  • Evidence-Based Verdicts: Uses a strict rubric to distinguish between successful runs, infrastructure bugs, and captured errors.
  • Use Case: Use this tool after an automated Asana-to-PR workflow to verify that the agent cleaned up its environment, didn't trigger a fork-storm, and adhered to the workspace status contract.

Quick Start

Run the orch-eval skill by providing the specific Asana GID for the agent run you wish to audit.

Frequently Asked Questions about orch-eval

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

FAQPage Schema
How do I audit autonomous agent infrastructure health after a run?

You can audit autonomous agent infrastructure health by evaluating logs, manifests, and system signals against a predefined ten-dimension rubric to grade orchestration stability and generate a comprehensive audit report.

What is orchestration stability grading for agent runs?

Orchestration stability grading evaluates autonomous agent runs across ten specific dimensions, including resource release, memory pressure, and slot citizenship, to distinguish successful operations from infrastructure bugs and captured errors.

How do I verify an automated agent cleaned up its environment and didn't trigger a fork-storm?

You verify environment cleanup and detect fork-storms by running an infrastructure audit using local forensics, memory monitors, and watchdog logs to check if the agent adhered to the workspace status contract.

Do I need local forensics and watchdog logs to evaluate agent run health?

Yes, evaluating agent run health requires access to local forensics, memory monitors, and watchdog logs to analyze operational footprints and generate a comprehensive evidence-based audit report.

Can I use this orchestration audit tool with an Asana-to-PR workflow?

Yes, you can use this audit tool after an automated Asana-to-PR workflow by providing the specific Asana GID to verify the agent run cleaned up its environment and adhered to workspace contracts.

What are the limitations of evaluating agent runs with a strict rubric?

The rubric-based evaluation requires complete access to local forensics and watchdog logs, meaning runs without proper manifest logging or system signal capture cannot be comprehensively graded across all ten dimensions.