happier-instruction-eval

Evaluates instruction variants through blinded organic tasks and behavior-based scoring.

1.6k|141|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/happier-dev/happier --skill happier-instruction-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: happier-instruction-eval
Source: https://github.com/happier-dev/happier/tree/main/skills/happier-instruction-eval
Command: npx skills add https://github.com/happier-dev/happier --skill happier-instruction-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changing instruction wording (constitutions, skills, agent guidelines) without evidence is guesswork. This Skill provides a controlled, blinded evaluation workflow that measures whether instruction variants actually change agent behavior, producing evidence for a human decision instead of relying on prose review or self-reported compliance.

Core Features & Use Cases

  • Blinded A/B Evaluation: Runs instruction variants under neutral labels with identical tasks, tools, and context so neither runner nor judge sees which variant is baseline or preferred.
  • Behavior-Based Scoring: Scores observable artifacts (sources read, edits made, tests run, claims reported) against a precommitted rubric rather than trusting self-reported compliance.
  • Advisory Synthesis: Produces an evidence-backed recommendation (retain, revise, combine, reject, or run a follow-up) without automatically mutating canonical instruction files.
  • Use Case: You want to know whether a new wording in your agent's constitution actually reduces scope drift. This Skill designs an organic task, runs both variants blind, judges the outputs under neutral labels, and reports which wording earned its place.

Quick Start

Ask the agent to evaluate two instruction variants using the happier-instruction-eval workflow with a controlled blinded comparison.

Frequently Asked Questions about happier-instruction-eval

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

FAQPage Schema
How do I evaluate whether an instruction change affects agent behavior?

Define the target behavior, fix a rubric of observable outcomes, then run each instruction variant on the same organic task under neutral labels. Score the resulting artifacts and tool evidence rather than self-reported compliance, and synthesize an advisory recommendation.

How do I run a blinded A/B test on agent instructions?

Hold the task prompt, repository basis, tools, permissions, and budget constant while varying only the instruction text. Label variants neutrally so runners and judges cannot see which is baseline, and isolate writes in separate temporary directories or worktrees.

When should I skip an instruction evaluation?

Skip evaluation when a source inspection or deterministic check can answer the question directly. The workflow is meant for cases where wording must demonstrably change routing, investigation, ownership, validation, or reporting behavior.

Does this evaluation modify my canonical instruction files?

No. The workflow is advisory only: it reports which wording earned its place and the smallest recommended edit, but never edits AGENTS.md or propagates variants without explicit change authority from the user.

What are the limitations of behavior-based instruction evaluation?

Results can be confounded by differing tools or models between runs, unavailable observations, and task variability. Confounds must be recorded explicitly, and repeated trials are only warranted when outcome variability is decision-material.