empirical-prompt-tuning

Run blinded subagents against a frozen evaluation design to improve agent-facing instructions.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill empirical-prompt-tuning-zenkakuhiragana
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: empirical-prompt-tuning
Source: https://github.com/ZenkakuHiragana/my-chezmoi-config/tree/main/dot_config/opencode/skills/empirical-prompt-tuning
Command: npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill empirical-prompt-tuning-zenkakuhiragana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Empirically improves agent-facing instructions by running blinded fresh subagents against a frozen evaluation design, scoring outputs with evidence-backed rubrics, and iterating until gains flatten out without hold-out regression.

Core Features & Use Cases

  • Fresh executors are blinded to scoring details to prevent bias
  • Frozen evaluation design with fixed scenarios and success criteria
  • Separate execution and scoring passes with evidence-backed decision rules
  • Iterative refinement of prompts, skills, and workflows to achieve stable gains

Quick Start

Deploy a fresh subagent, run it against the frozen evaluation plan, and record scoring evidence to guide iterative improvements.

Frequently Asked Questions about empirical-prompt-tuning

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

FAQPage Schema
How do I improve agent prompts when ambiguous wording limits success?▼

Empirical prompt tuning improves agent-facing instructions by running blinded fresh subagents against a frozen evaluation design to reveal ambiguities and drive measurable improvements. This process applies to prompts, skills, command workflows, and code-generation prompts.

What is blinded evaluation in prompt tuning and how does it prevent bias?▼

Blinded evaluation in prompt tuning prevents bias by using fresh executors unaware of scoring details, running separate execution and scoring passes with evidence-backed decision rules. This ensures outputs are judged strictly on rubric criteria rather than executor expectations.

How do I run an empirical prompt tuning workflow step by step?▼

To run empirical prompt tuning, freeze an evaluation design with fixed scenarios and success criteria, deploy a fresh subagent to run against it, record scoring evidence separately, and iterate on the prompts until gains flatten without hold-out regression.

Can I use empirical prompt tuning for code-generation prompts and AGENTS sections?▼

Yes, empirical prompt tuning applies to code-generation prompts, AGENTS sections, command workflows, and skills. Any agent-facing instructions where ambiguous wording limits success are valid targets for blinded evaluation and iterative refinement.

What's the best way to evaluate prompt quality without executor bias?▼

The best way to evaluate prompt quality without executor bias is to apply a frozen experiment plan with blinded executors and separate scoring passes. This approach isolates prompt ambiguities by using evidence-backed rubrics and fresh subagents.

When should I stop iterating during empirical prompt tuning?▼

You should stop iterating during empirical prompt tuning when measurable gains flatten out and no hold-out regression occurs. This indicates the agent-facing instructions have reached stable success against the frozen evaluation design and evidence-backed rubrics.