octocode-graph-eval

Evaluates agent work with KPI contracts, baselines, and keep/discard improvement loops.

921|75|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-graph-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: octocode-graph-eval
Source: https://github.com/bgauryy/octocode-mcp/tree/main/skills/octocode-graph-eval
Command: npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-graph-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Agents and teams claim improvements without baselines, held-out checks, or keep/discard discipline, leading to vibe-based decisions, contaminated benchmarks, and multi-agent graphs that agree with themselves instead of verifying results.

Core Features & Use Cases

  • Goal-to-KPI cascade: Converts user goals into measurable primary KPIs, leading indicators, guardrails, and binary decision rules before any change is made.
  • Nested improvement loops: Runs experiment (keep/discard), suite (grow eval cases from error analysis), and meta/bilevel loops that rewrite the search strategy when the inner loop goes flat.
  • Graph-of-loops evaluation: Audits multi-agent workflows for fake parallelism, shared-context verifiers, Goodhart metric drift, and missing anchor nodes, with per-node sensors and attribution by bisection.
  • Use Case: A team's support bot improved ticket-resolution rate 30% while satisfaction dropped; the skill detects the Goodhart failure, halts the loop, and reframes the goal with a counter-metric guardrail.

Quick Start

Ask the agent to define a KPI contract with baseline, target, and guardrails, then run a keep/discard improvement loop against a runnable sensor until the target is met.

Frequently Asked Questions about octocode-graph-eval

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

FAQPage Schema
How do I run a keep/discard improvement loop for an AI agent?

Freeze the eval harness, record a baseline under a fixed budget, make the smallest subject change, then re-measure with the same command. Keep the change only if the primary KPI improves and guardrails hold; otherwise discard it and log the hypothesis.

How do I evaluate a multi-agent workflow or agent graph?

Set the primary KPI at the graph boundary, add per-node sensors, and run edge detection to confirm real dependencies before parallelizing. Attribute failures by bisecting nodes with frozen inputs, and require fresh-context verifiers plus at least one anchor node with deterministic evidence.

Should I gate releases on public benchmarks like SWE-bench Verified?

No. Public benchmarks are orientation signals only because of contamination and saturation risk. Build a private eval suite from your own real failure traces and use it as the ship gate, treating public scores as weak evidence without transcript audits.

What is Goodhart's Law in agent evaluation and how do I guard against it?

Goodhart's Law means a loop optimizing one metric can hit it while the real goal degrades, such as resolution rate rising while satisfaction falls. Assign every primary KPI a counter-metric guardrail the agent cannot tune, and reframe the goal when the guardrail degrades.

When should I escalate from an experiment loop to a meta or bilevel loop?

Escalate when the primary metric stays flat across many trials and error analysis finds no new failure categories. A bilevel outer loop reads the inner loop's execution trace and rewrites the search strategy itself, rather than running more inner trials or editing graders.

Why is a verifier that shares the executor's context not independent?

A verifier receiving the executor's full conversation history is agreeing with itself in a different font, not verifying. Require each verifier node to start with fresh context and grade only the artifact before calling a result verified.