prompt-tune

Evaluate and tune Myco LLM prompts using structured fixtures and EVAL_MODEL.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill prompt-tune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-tune
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/prompt-tune
Command: npx skills add https://github.com/goondocks-co/myco --skill prompt-tune

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps development teams tune and evaluate Myco's LLM prompts to improve reliability, safety, and usefulness across internal AI workflows.

Core Features & Use Cases

  • Evaluate prompts against structured fixtures to surface weaknesses and edge cases.
  • Compare different models and prompt iterations to identify best-performing configurations.
  • Document prompt changes and learning in a reference log to enable traceability and reuse.

Quick Start

Run the prompt tuning workflow against your prompt fixtures to start evaluating and iterating on prompts.

Frequently Asked Questions about prompt-tune

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

FAQPage Schema
How do I evaluate LLM prompts against test fixtures?

You evaluate LLM prompts by running a tuning workflow against structured test fixtures stored under tests/prompts, which surfaces weaknesses and edge cases by comparing model outputs against expected results.

What is prompt tuning and how does model comparison work?

Prompt tuning iterates on prompt configurations while model comparison benchmarks different LLMs using the EVAL_MODEL variable, identifying best-performing setups by testing iterations against your structured fixtures.

How do I start prompt testing for Myco's AI agents?

Start prompt testing by organizing test fixtures and scripts under tests/prompts, then executing the tuning workflow to apply structured evaluation across development workflows for Myco's AI agents.

Do I need specific file structures for prompt evaluation?

Yes, prompt evaluation requires fixtures and testing scripts stored under tests/prompts, a model selection defined by the EVAL_MODEL variable, and a documented methodology in references for traceability.

What's the best way to document prompt changes and iterations?

Document prompt changes and learning in a reference log to enable traceability and reuse, storing a documented methodology in references so structured evaluation outcomes are recorded for future iterations.

Can I compare different LLM models using the same prompt fixtures?

Yes, you compare different models and prompt iterations using the same structured fixtures by selecting an evaluation model with the EVAL_MODEL variable, identifying best-performing configurations across Myco's LLMs.