opt-prompt-eval

Log post-task performance metrics and session data for prompt decisions.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hjung3113/vocpage --skill opt-prompt-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opt-prompt-eval
Source: https://github.com/hjung3113/vocpage/tree/main/.claude/skills/opt-prompt-eval
Command: npx skills add https://github.com/hjung3113/vocpage --skill opt-prompt-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires append.sh, session-stats.sh, and includes scripts (resource) components.

What problem does it solve?

This Skill enables precise recording of post-task retrospective data for normalized prompts, maintaining accountability and improving prompt workflows.

Core Features & Use Cases

  • Retro Log Recording: Writes a JSONL row with detailed metrics after a prompt task completes.
  • Traceability: Links retro entries to specific decision IDs and session contexts.
  • Use Case: A team reviews a prompt’s performance by capturing latency and token usage after closure, facilitating continuous optimization.

Quick Start

Invoke /opt-prompt-eval <decision_id> after prompt completion to log retro data for analysis.

Frequently Asked Questions about opt-prompt-eval

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

FAQPage Schema
How do I log prompt evaluation metrics after a task completes?

To log prompt evaluation metrics after a task completes, invoke the retro logging command with a specific decision ID to automatically write a JSONL row capturing session data and performance insights.

What is the best way to ensure traceability for prompt decisions and session contexts?

Ensuring traceability for prompt decisions involves linking retrospective log entries to specific decision IDs and session contexts, providing structured accountability for post-task performance analysis.

How do I record post-task performance data like latency and token usage for prompt refinement?

Recording post-task performance data like latency and token usage is handled by automated Python scripts and shell helpers that write structured JSONL logs for continuous prompt optimization.

Do I need a specific decision ID to start logging retrospective prompt data?

Yes, you need a specific decision ID to start logging retrospective prompt data, as passing this identifier triggers the automated capture of session metrics and ensures data traceability.

When do I need to use JSONL logs for prompt evaluation?

You need to use JSONL logs for prompt evaluation when your team requires structured retrospective insights and data integrity for analyzing post-task performance metrics and refining prompt workflows.

What are the limitations of using shell helpers for prompt evaluation logging?

Limitations of using shell helpers for prompt evaluation logging include dependencies on specific script components like append.sh and session-stats.sh to maintain data consistency and execute the automated logging process correctly.