Skip to content
Back to skills

Prove Whether A Prompt Or Model Variant Really Won Before Shipping With Promptstats

ASecurity

Run statistically sound comparisons on eval results so prompt and model changes are judged by confidence bounds, not bar-chart vibes.

  • 36 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 2, 2026
ai-agentspythongogitapisecuritydocumentation

Works with

  • terminal
  • api

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned June 2, 2026

npx -y skills add agentskillexchange/skills --skill prove-whether-a-prompt-or-model-variant-really-won-before-shipping-with-promptstats --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prove Whether A Prompt Or Model Variant Really Won Before Shipping With Promptstats?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prove Whether A Prompt Or Model Variant Really Won Before Shipping With Promptstats
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agentskillexchange-prove-whether-a-prompt-or-model-variant-really-won/badge)](https://www.skillsdirectory.com/skills/agentskillexchange-prove-whether-a-prompt-or-model-variant-really-won)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "Prove whether a prompt or model variant really won before shipping with promptstats"
slug: "prove-whether-a-prompt-or-model-variant-really-won-before-shipping-with-promptstats"
description: "Run statistically sound comparisons on eval results so prompt and model changes are judged by confidence bounds, not bar-chart vibes."
github_stars: 97
verification: "security_reviewed"
source: "https://github.com/ianarawjo/promptstats"
author: "Ian Arawjo"
publisher_type: "individual"
category: "Code Quality & Review"
framework: "Multi-Framework"
tool_ecosystem:
  github_repo: "ianarawjo/promptstats"
  github_stars: 97
  npm_package: "promptstats"
  npm_weekly_downloads: 678
---

# Prove whether a prompt or model variant really won before shipping with promptstats

Run statistically sound comparisons on eval results so prompt and model changes are judged by confidence bounds, not bar-chart vibes.

## Prerequisites

Python environment, promptstats package, eval result tables or per-input score arrays, prompt or model experiment outputs to compare

## Installation

Use the upstream install or setup path that matches your environment:
- pip install evalstats
- pip install "evalstats[xlsx]"
- pip install "evalstats[all]"
- pip install "evalstats[lmm]"

Requirements and caveats from upstream:
- If you set method="lmm", analyze() switches to a mixed-effects path (score ~ template + (1|input)) with Wald CIs and parametric rank distributions. By default this uses statsmodels (pure Python, no additional setup re...
- ## Python API
- evalstats main use case is as a Python API, which provides a similar entry point, the analyze() function. Simply pass your benchmark data in the correct format, and pass it to analyze to get a battery of results:

Basic usage or getting-started notes:
- What statistics test should I run in X situation?
- as well as example code (which will, obviously, tend to use evalstats, but
- Running estats.analyze() and then estats.print_analysis_summary(analysis) prints a full statistical report to the terminal, including confidence interval line plots, pairwise comparisons between prompt templates, and...

- Source: https://github.com/ianarawjo/promptstats
- Extracted from upstream docs: https://raw.githubusercontent.com/ianarawjo/promptstats/HEAD/README.md

## Documentation

- https://statsforevals.com

## Source

- [Agent Skill Exchange](https://agentskillexchange.com/skills/prove-whether-a-prompt-or-model-variant-really-won-before-shipping-with-promptstats/)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.