empirical-prompt-tuning

Run prompts through subagents and collect dual feedback to iteratively refine them.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SatohaCC/nextjs-mdx-blog --skill empirical-prompt-tuning-satohacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: empirical-prompt-tuning
Source: https://github.com/SatohaCC/nextjs-mdx-blog/tree/main/.agents/skills/empirical-prompt-tuning
Command: npx skills add https://github.com/SatohaCC/nextjs-mdx-blog --skill empirical-prompt-tuning-satohacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

agent 向けテキスト指示(skill / slash command / タスクプロンプト / CLAUDE.md 節 / コード生成プロンプト)を、バイアスを排した実行者に動かしてもらい、両面(実行者の自己申告 + 指示側メトリクス)で評価して反復改善する手法。改善が頭打ちになるまで回す。

Core Features & Use Cases

  • 実行者と指示側の両面評価を組み合わせ、プロンプトの曖昧さを解消する反復ワークフローを提供。
  • 新規作成・大幅改訂直後や、エージェントの挙動が期待通りでない場合の安定化を支援。
  • 監査可能なレポートとツール使用履歴を含む、再現性の高い評価プロセスを提供。

Quick Start

Dispatch a subagent to run an empirical evaluation of a target prompt and report back with dual-sided metrics to drive iterative improvement.

Frequently Asked Questions about empirical-prompt-tuning

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

FAQPage Schema
How do I iteratively improve agent prompts when behavior is unpredictable?

Iterative prompt improvement requires running target prompts through subagents and collecting dual feedback to evaluate and refine instructions until performance stabilizes. This empirical prompt tuning process uses structured metrics to eliminate ambiguity and validate behavior.

What is empirical prompt tuning and how does the dual evaluation mechanism work?

Empirical prompt tuning evaluates agent instructions by combining the subagent's self-reported execution feedback with the instruction-side evaluation metrics. This dual-sided approach identifies behavioral mismatches and drives iterative refinement cycles until improvements plateau.

How to validate revised agent skills or slash commands for robust behavior?

Validate revised agent skills or slash commands by dispatching subagents to execute the target instructions and report back with structured evaluation metrics. Repeatable cycles driven by YAML-frontmatter configuration ensure auditable validation with tool usage and duration reports.

When do I need empirical prompt evaluation for my agent instructions?

Empirical prompt evaluation is needed immediately after creating or substantially revising agent prompts, skills, or slash commands. It stabilizes unpredictable agent behavior by running repeatable evaluation cycles with audit-ready reports containing tool usage history and execution duration.

Does empirical prompt tuning require specific dependencies or component libraries?

Empirical prompt tuning operates without external dependencies or component libraries. It relies entirely on dispatching internal subagents and utilizing YAML-frontmatter driven configuration to structure the evaluation metrics and generate audit-ready reports.

What are the limitations of using subagent feedback for prompt evaluation?

Subagent feedback for prompt evaluation is limited by the plateauing of iterative improvements over repeated cycles. While dual-sided metrics reduce ambiguity, the process requires running until improvements stall, which may consume significant execution time and tool usage overhead.