From Feelings to Metrics: Understanding and Formalizing How Users Vibe-Test LLMs
Organizations: Technion – Israel Institute of Technology · The Hebrew University of Jerusalem
Abstract
Evaluating LLMs is challenging, as benchmark scores often fail to capture models' real-world usefulness. Instead, users often rely on ``vibe-testing'': informal experience-based evaluation, such as comparing models on coding tasks related to their own workflow. While prevalent, vibe-testing is often too ad hoc and unstructured to analyze or reproduce at scale. In this work, we study how vibe-testing works in practice and then formalize it to support systematic analysis. We first analyze two empirical resources: (1) a survey of user evaluation practices, and (2) a collection of in-the-wild model comparison reports from blogs and social media. Based on these resources, we formalize vibe-testing as a two-part process: users personalize both what they test and how they judge responses. We then introduce a proof-of-concept evaluation pipeline that follows this formulation by generating personalized prompts and comparing model outputs using user-aware subjective criteria. In experiments on coding benchmarks, we find that combining personalized prompts and user-aware evaluation can change which model is preferred, reflecting the role of vibe-testing in practice. These findings suggest that formalized vibe-testing can serve as a useful approach for bridging benchmark scores and real-world experience.
Figures & tables
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | Researcher | Advanced |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.03 * (0.00) | 0.01 * (0.00) | 0.08 * (0.02) | 0.91 * (0.01) |
| Personalized | 0.77 * (0.02) | 0.55 * (0.02) | 0.43 * (0.01) | 0.58 * (0.03) | |
| Control | 0.06 * (0.00) | 0.02 * (0.00) | 0.10 * (0.02) | 0.93 * (0.01) | |
| GPT-5.1 vs. GPT-4o | Original | 0.09 * (0.00) | 0.16 * (0.02) | 0.63 * (0.02) | 0.88 * (0.00) |
| Personalized | 0.94 * (0.01) | 0.77 * (0.02) | 0.97 * (0.00) | 0.82 * (0.02) | |
Appendix figures & tables39 assets
Supplementary material from the paper’s appendix.
Appendix
| Input Dimension | Operational Meaning | Typical Cues |
|---|---|---|
| Task type | The kind of task used as the test, ranging from short, isolated prompts to multi-step scenarios (e.g., single-turn coding, debugging, planning, writing, workflow tasks). | Mentions of “my daily workflow,” “I tried debugging,” “I asked it to plan,” or explicit task categories (code generation, refactor, summarization, reasoning). |
| Task complexity | How demanding the test is in length, number of constraints, required steps, and need for long-range coherence. | Short one-shot prompts vs. long prompts with many requirements, multi-step instructions, or tasks requiring sustained structure. |
| Real-world context | Whether the prompt situates the task in a concrete domain or scenario (personal, professional, or everyday), rather than an abstract benchmark-like query. | “In my codebase,” “for my project,” “as a product manager,” “explain like cooking,” domain-specific details, constraints, or artifacts. |
| Persona-based framing | How the user frames the interaction style, role, or audience (tutor vs. peer, novice vs. expert, tone requirements). | “Explain to a beginner,” “be concise,” “act as a senior engineer,” “write like a legal memo,” explicit tone or audience constraints. |
| Underspecification level | How much the prompt leaves implicit, to test the model’s ability to ask clarifying questions, make reasonable assumptions, or handle ambiguity. | Vague instructions on purpose (“do something better”), missing details, open-ended tasks, or explicit stress-tests of ambiguity handling. |
| Constraint tightness | How strictly the prompt constrains format, tools, style, or rules (schemas, word limits, citation rules, refusal constraints). | “Return JSON with this schema,” “no markdown,” “must cite sources,” “do not use X,” strict formatting or policy constraints. |
| Output Dimension | Operational Meaning | Typical Cues |
|---|---|---|
| Comparison setup | How the user elicits and compares outputs, including side-by-side comparisons, reruns, and multi-prompt probing. | “I compared A vs. B,” “ran it twice,” “tried a few variants,” “it was inconsistent across runs.” |
| Correctness | Whether the output is correct with respect to the task requirements and stated constraints. | Explicit correctness judgments (“it works,” “it is wrong,” “hallucinated”), tests with executable code, or fact-check claims. |
| Clarity | How readable and well organized the response is for the intended user, including logical flow and formatting. | Mentions of “easy to follow,” “well structured,” “confusing,” “jumps around,” “good explanation.” |
| Cognitive load | How mentally taxing the response is, given chunking, ordering, and amount of new concepts introduced at once. | “Too much at once,” “overwhelming,” “nice step-by-step,” “dumped details,” “hard to track.” |
| Style/Tone fit | Alignment with the requested or expected tone, persona, and communication style for the user context. | “Too formal,” “felt friendly,” “matches my style,” “sounds like marketing,” “too robotic.” |
| Workflow fit | Whether the output integrates into the user’s actual workflow, helping them complete the task with minimal friction. | “I can paste this into my codebase,” “saved me time,” “usable,” “does not match how I work,” “not actionable.” |
| Profile | Description and Preference Weights |
|---|---|
| Beginner Student | ”I am an undergraduate student with limited Python experience, mainly using it for basic data analysis in my statistics courses. I need code that is very clear and well-explained.” Weights: Clarity: 5, Style: 1, Workflow Fit: 2, Cognitive Load: 1, Context Awareness: 4, Persona Consistency: 4, Anthropomorphism: 5. |
| Intermediate Learner | ”I have moderate coding experience and typically work on debugging and small projects. I care most about getting the correct solution, and I appreciate helpful clarifications that support my learning as I go.” Weights: Clarity: 5, Style: 1, Workflow Fit: 3, Cognitive Load: 1, Context Awareness: 4, Persona Consistency: 4, Anthropomorphism: 3. |
| AI Researcher | ”I am a researcher in the field of machine learning. I need code that is efficient and easy to modify and trace.” Weights: Clarity: 4, Style: 1, Workflow Fit: 4, Cognitive Load: 1, Context Awareness: 4, Persona Consistency: 4, Anthropomorphism: 1. |
| Advanced Developer | ”I am an experienced programmer and I often work on optimization and complex debugging. I prefer efficient solutions with minimal guidance and concise outputs.” Weights: Clarity: 3, Style: 1, Workflow Fit: 5, Cognitive Load: 1, Context Awareness: 4, Persona Consistency: 4, Anthropomorphism: 1. |
| Win-rate (Tie-rate) | |||||
|---|---|---|---|---|---|
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.03 * (0.01) | 0.02 * (0.01) | 0.12 * (0.02) | 0.85 * (0.00) |
| Personalized | 0.60 * (0.05) | 0.63 * (0.03) | 0.39 * (0.01) | 0.63 * (0.03) | |
| Control | 0.12 * (0.01) | 0.10 * (0.01) | 0.20 * (0.02) | 0.87 * (0.01) | |
| GPT-5.1 vs. GPT-4o | Original | 0.13 * (0.01) | 0.22 * (0.03) | 0.68 * (0.03) | 0.92 * (0.01) |
| Personalized | 0.90 * (0.01) | 0.90 * (0.02) | 0.85 * (0.01) | 0.85 * (0.02) | |
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.04 * (0.00) | 0.01 * (0.01) | 0.03 * (0.02) | 0.82 * (0.00) |
| Personalized | 0.40 * (0.03) | 0.55 * (0.05) | 0.48 (0.12) | 0.45 * (0.10) | |
| Control | 0.04 * (0.00) | 0.02 * (0.01) | 0.03 * (0.02) | 0.84 * (0.01) | |
| Qwen3-32B vs. Qwen3-14B | Original | 0.56 (0.10) | 0.58 * (0.08) | 0.61 * (0.09) | 0.46 (0.07) |
| Personalized | 0.64 * (0.01) | 0.63 * (0.07) | 0.61 * (0.08) | 0.41 (0.17) | |
| Grouping | Subset | Agreement (%) | Fleiss’s |
|---|---|---|---|
| Model pair | GPT-5.1 vs. GPT-OSS-20B | 0.82 0.14 | 0.38 0.21 |
| GPT-5.1 vs. GPT-4o | 0.85 0.10 | 0.38 0.12 | |
| Gemini-3-Pro vs. Gemma-3-4B | 0.82 0.07 | 0.49 0.13 | |
| Qwen3-32B vs. Qwen3-14B | 0.64 0.07 | 0.30 0.12 | |
| Persona | Beginner | 0.81 0.13 | 0.36 0.10 |
| Intermediate | 0.78 0.13 | 0.45 0.18 |
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.09 * (0.02) | 0.15 * (0.07) | 0.61 * (0.06) | 0.87 * (0.04) |
| Personalized | 0.92 * (0.03) | 0.75 * (0.07) | 0.93 * (0.04) | 0.74 * (0.06) | |
| Control | 0.08 * (0.03) | 0.18 * (0.07) | 0.69 * (0.06) | 0.93 * (0.03) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.04 * (0.02) | 0.01 * (0.02) | 0.08 * (0.05) | 0.91 * (0.02) |
| Personalized | 0.73 * (0.06) | 0.53 (0.10) | 0.38 * (0.09) | 0.53 (0.07) | |
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.09 * (0.00) | 0.16 * (0.02) | 0.63 * (0.02) | 0.88 * (0.00) |
| Personalized | 0.94 * (0.01) | 0.77 * (0.02) | 0.97 * (0.00) | 0.82 * (0.02) | |
| Control | 0.08 * (0.01) | 0.19 * (0.03) | 0.70 * (0.02) | 0.95 * (0.01) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.03 * (0.00) | 0.01 * (0.00) | 0.08 * (0.02) | 0.91 * (0.01) |
| Personalized | 0.77 * (0.02) | 0.55 * (0.02) | 0.43 * (0.01) | 0.58 * (0.03) | |
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.08 * (0.01) | 0.16 * (0.03) | 0.61 * (0.04) | 0.86 * (0.01) |
| Personalized | 0.93 * (0.01) | 0.75 * (0.03) | 0.95 * (0.01) | 0.82 * (0.03) | |
| Control | 0.07 * (0.01) | 0.17 * (0.04) | 0.68 * (0.04) | 0.94 * (0.01) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.04 * (0.00) | 0.01 * (0.00) | 0.07 * (0.06) | 0.92 * (0.01) |
| Personalized | 0.76 * (0.03) | 0.57 * (0.04) | 0.37 * (0.03) | 0.56 * (0.04) | |
| Win-rate (Tie-rate) | |||||
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.09 * (0.00) | 0.16 * (0.02) | 0.72 * (0.02) | 0.91 * (0.00) |
| Personalized | 0.96 * (0.00) | 0.78 * (0.02) | 0.98 * (0.00) | 0.84 * (0.02) | |
| Control | 0.06 * (0.01) | 0.15 * (0.02) | 0.79 * (0.02) | 0.94 * (0.01) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.05 * (0.00) | 0.04 * (0.00) | 0.06 * (0.00) | 0.94 * (0.00) |
| Personalized | 0.80 * (0.06) | 0.55 (0.01) | 0.32 * (0.15) | 0.58 * (0.04) | |
| Win-rate (Tie-rate) | |||||
|---|---|---|---|---|---|
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.14 * (0.00) | 0.21 * (0.01) | 0.60 * (0.01) | 0.87 * (0.00) |
| Personalized | 0.93 * (0.01) | 0.76 * (0.01) | 0.96 * (0.00) | 0.75 * (0.03) | |
| Control | 0.09 * (0.01) | 0.22 * (0.04) | 0.65 * (0.03) | 0.94 * (0.00) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.07 * (0.00) | 0.04 * (0.00) | 0.04 * (0.00) | 0.88 * (0.02) |
| Personalized | 0.72 * (0.04) | 0.53 (0.03) | 0.20 * (0.03) | 0.40 * (0.04) | |
| Win-rate (Tie-rate) | |||||
|---|---|---|---|---|---|
| Model Pair | Prompt Type | Beginner | Intermediate | AI Researcher | Advanced |
| GPT-5.1 vs. GPT-4o | Original | 0.02 * (0.93) | 0.02 * (0.93) | 0.03 * (0.93) | 0.04 (0.93) |
| Personalized | 0.15 * (0.84) | 0.20 * (0.73) | 0.31 * (0.68) | 0.14 * (0.84) | |
| Control | 0.02 * (0.94) | 0.02 * (0.94) | 0.04 * (0.94) | 0.04 * (0.94) | |
| GPT-5.1 vs. GPT-OSS-20B | Original | 0.02 * (0.94) | 0.01 * (0.94) | 0.01 * (0.94) | 0.03 (0.94) |
| Personalized | 0.10 * (0.86) | 0.15 * (0.68) | 0.18 * (0.63) | 0.11 * (0.85) | |
| Win-rate | ||
| User Profile | Original | Personalized |
| Beginner Student | 0.03 | 0.77 |
| Advanced Developer | 0.91 | 0.58 |
| Reddit Beginner | 0.04 | 0.68 |
| YouTube Advanced | 0.28 | 0.53 |
| Prompt Type | Judge Pair Type | Agreement (%) | Cohen’s | #Pairs | #Items |
|---|---|---|---|---|---|
| Original | LLM–LLM | 90.9 4.5 | 0.81 0.10 | 3 | 66 |
| Human–Human | 94.4 15.0 | 0.80 0.39 | 15 | 35 | |
| Human–LLM | 89.5 15.6 | 0.78 0.33 | 18 | 141 | |
| Personalized | LLM–LLM | 100.0 0.0 | 1.00 0.00 | 3 | 30 |
| Human–Human | 40.0 43.1 | -0.17 0.58 | 15 | 24 | |
| Human–LLM | 50.0 21.0 | -0.06 0.32 | 18 | 72 |
| Dimension | Pair Type | Agr. (%) | Agr. excl. ties (%) | excl. ties | |
|---|---|---|---|---|---|
| Clarity | Overall | 54.4 30.8 | 0.27 0.32 | 73.6 25.1 | 0.40 0.42 |
| LLM–LLM | 69.7 6.9 | 0.43 0.10 | 88.1 6.1 | 0.70 0.15 | |
| Human–Human | 48.7 40.2 | 0.20 0.34 | 75.0 34.5 | 0.34 0.47 | |
| Human–LLM | 56.6 23.2 | 0.30 0.33 | 70.3 19.1 | 0.38 0.42 | |
| Tone/Style Fit | Overall | 92.3 11.4 | 0.81 0.23 | 97.6 5.5 | 0.92 0.16 |
| LLM–LLM | 90.9 4.5 | 0.78 0.11 | 100.0 0.0 | 1.00 0.00 |
| Dimension | Pair Type | Agr. (%) | Agr. excl. ties (%) | excl. ties | |
|---|---|---|---|---|---|
| Clarity | Overall | 28.5 32.7 | -0.04 0.35 | 47.6 38.4 | -0.13 0.64 |
| LLM–LLM | 83.3 5.8 | 0.71 0.08 | 96.7 5.8 | 0.93 0.12 | |
| Human–Human | 20.0 36.8 | -0.13 0.32 | 35.7 47.6 | -0.20 0.45 | |
| Human–LLM | 26.4 21.8 | -0.11 0.22 | 43.3 30.7 | -0.33 0.53 | |
| Tone/Style Fit | Overall | 39.7 35.3 | 0.08 0.41 | 69.6 38.7 | 0.28 0.54 |
| LLM–LLM | 76.7 11.5 | 0.64 0.18 | 95.2 8.2 | 0.91 0.16 |
| # | Source | Title |
|---|---|---|
| 1 | Youtube | Google’s nano banana just killed Photoshop… let’s run it |
| 2 | Youtube | GPT-5 is here… Can it win back programmers? |
| 3 | Youtube | Google’s Genie model makes realistic worlds in realtime… |
| 4 | Youtube | Is Elon’s Grok 3 the new AI king? |
| 5 | Youtube | I Tested Gemini 3 Pro (it did really well) |
| 6 | Youtube | Claude 4 vs GPT-5: Which AI is actually better? |
| # | Source | Title |
|---|---|---|
| 21 | GPT-5 vs Claude 4 for coding: which feels better? | |
| 22 | GPT-4o feels different, anyone else? | |
| 23 | What model do you prefer for writing and why? | |
| 24 | Benchmarks say X, but I keep using Y (reasons) | |
| 25 | Llama 3 vs Claude: vibes and reliability | |
| 26 | Which model has better tone for tutoring? |
| Question | Responses (%) |
|---|---|
| AI tool usage frequency. How often do you use AI tools (e.g., ChatGPT, Claude, Gemini, Copilot)? | Daily: 92.2% Several times per week: 7.8% |
| Primary use cases. What do you mainly use AI systems for? (multi-select) | Coding / debugging: 88.2% Writing / communication: 70.6% Learning / tutoring: 56.9% Complex reasoning / problem-solving: 37.3% Productivity: 35.3% Creative tasks: 33.3% Entertainment: 23.5% Other (free-text): 6.0% |
| Technical background. How would you describe your technical background? | Technical (e.g., engineering, data science, CS background): 47.1% AI/ML expert: 47.1% Somewhat technical: 5.9% |
| Question | Responses (%) |
|---|---|
| Vibe-testing familiarity. Have you ever vibe-tested an AI model? | Yes: 82.4% Not sure: 13.7% No: 3.9% |
| Exploration frequency. When using a new AI model, how often do you experiment with prompts or tasks just to see how it behaves? (1 = never, 7 = very often) | 1: 2.0% 2: 4.1% 3: 6.1% 4: 8.2% 5: 32.7% 6: 22.4% 7: 24.5% |
| Typical vibe-testing actions. Which of the following do you typically do when vibe-testing? (multi-select) | Try tasks from my own workflow: 73.5% Compare outputs from different models: 65.3% Check tone, style, or personality: 49.0% Give vague or underspecified instructions (ambiguity stress-test): 44.9% Use a small set of personal “test prompts”: 38.8% Re-run the same prompt (stability / consistency): 38.8% Other (free-text): 6.0% |
| Vibe-testing domains. In which domains do you most often vibe-test AI tools? (multi-select) | Coding / software development: 65.3% Writing / communication: 51.0% Reasoning / problem-solving: 44.9% Learning / tutoring: 28.6% Creative tasks: 28.6% Productivity: 14.3% Other (free-text): 6.0% |
| Judgment criteria. When evaluating a model’s responses, which aspects matter most to you? (multi-select) | Correctness / accuracy: 91.8% Clarity and structure: 59.2% Fit for my personal workflow: 40.8% Tone / style: 32.7% Ability to resolve ambiguity: 18.4% Efficiency / conciseness: 16.3% Stability / consistency: 20.4% Other (free-text): 14.0% |
| Question | Responses (%) |
|---|---|
| Semi-consistent prompt set. Do you have a semi-consistent set of prompts or tasks that you use when testing a new model? (Even just one) | Improvised: 51.1% Partially consistent: 34.7% Consistent set: 10.2% |
| Golden prompt existence. Do you have a “Golden Prompt” (a specific test you always use to quickly judge a model’s quality)? | Yes: 18.4% No: 73.5% Not sure: 8.2% |
| Golden prompt content. If yes, please provide your “Golden Prompt” here. | Open-ended; omitted for anonymization. |
| Example prompt/task and what to look for. Please give one example of a prompt or task you might use when testing a model. Briefly say what you look for in the response. | Open-ended; omitted for anonymization. |
| Consent to publish prompts. May we include your prompts in our public report? | Yes (anonymously): 46.8% Yes (with acknowledgement): 4.3% No: 48.9% |
| Question | Responses (%) |
|---|---|
| Benchmark awareness. Are you aware of the published performance scores (benchmarks) of the models you use? | Yes: 46.9% Somewhat: 42.9% No: 10.2% |
| Alignment with benchmarks. How closely do your personal impressions of models match their published benchmark results? (1 = not at all, 7 = very closely) | 1: 0.0% 2: 13.6% 3: 9.1% 4: 27.3% 5: 36.4% 6: 13.6% 7: 0.0% |
| Benchmark mismatch. Have you ever found that a model felt significantly better or worse than its reported scores suggested? | Yes: 86.4% Not sure: 11.4% No: 2.3% |
| What benchmarks miss. Which aspects do you feel benchmarks fail to measure well? (multi-select) | Fit for my workflow: 61.4% Style, tone, or personality: 40.9% Handling ambiguity / underspecification: 34.1% Stability and consistency: 31.8% Trustworthiness / safety: 27.3% Clarity and readability: 27.3% Other: 13.6% |
| Value of vibe-testing. How valuable is vibe-testing for evaluating AI systems? (1 = not valuable, 7 = very valuable) | 1: 0.0% 2: 0.0% 3: 2.0% 4: 22.4% 5: 38.8% 6: 18.4% 7: 18.4% |
| Interest in automation. If there were an automated tool that produced a personalized vibe-test for you, would you use it? | Yes: 32.7% Maybe: 51.0% No: 8.2% Other (free-text): 8.0% |
LLM Evaluation
Large language model evaluation measures what models can do, how reliably they do it, and whether benchmark scores predict real-world performance.
See all 2,364 papers