Eval-driven development: build a real eval pipeline for Python LLM apps
Instrument your Python LLM app with pixie-qa — define eval criteria, build golden datasets, run real evals with LLM-as-judge scorers, analyze results into an action plan
- What
- Instrument your Python LLM app with pixie-qa — define eval criteria, build golden datasets, run real evals with LLM-as-judge scorers, analyze results into an action plan
- Cost
- Free
- Needs
- a Python (3.10+) LLM application to evaluate; the pixie-qa package (the skill's resources/setup.sh installs it) — the skill is a guided workflow, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @github's eval-driven development skill for Python LLM applications, powered by the pixie-qa package: a 6-step agent workflow. Step 1, analyze the app and define eval criteria derived from real failure modes (not generic quality dimensions). Step 2, instrument the app with `wrap()` calls at its data boundaries, write a Runnable that invokes the real entry point, and capture a reference trace. Step 3, turn criteria into runnable evaluators (the agent evaluator is the default for semantic criteria, custom functions only for mechanical checks). Step 4, build a golden dataset from real-world data — never the project's own test fixtures. Step 5, run `pixie test` until it completes with real scores. Step 6, analyze outcomes and write a prioritized action plan. Hard rules: the app's LLM calls must go to a REAL LLM — no mocking, no faking, or scores are meaningless; a web server (`pixie start`) runs alongside for live result viewing. Honest caveats: methodology plus tooling — the pixie-qa package and its web server are prerequisites (setup.sh in the skill); running evals makes real LLM API calls (real API costs); Python 3.10+. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Eval-driven development is a free skill from @github for Python LLM applications, powered by pixie-qa, in a 6-step workflow. It defines criteria from real failure modes, instruments the app with wrap calls and a Runnable, turns criteria into evaluators, builds a golden dataset from real data, never test fixtures, and runs pixie test until scores appear.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 82701c2Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Python (3.10+) LLM application to evaluate; the pixie-qa package (the skill's resources/setup.sh installs it) — the skill is a guided workflow, not software Install "Eval-driven development: build a real eval pipeline for Python LLM apps" for me. It gives my agent @github's eval-driven workflow: analyze the Python LLM app and define eval criteria from real failure modes, instrument data boundaries with wrap() calls, write a Runnable against the real entry point, capture a reference trace, build runnable evaluators (agent evaluators for semantic criteria), create a golden dataset from real-world data, run pixie test to real scores, and produce a prioritized action plan. MIT-licensed. Repository: https://raw.githubusercontent.com/github/awesome-copilot/82701c24b99488536ca399ff4789a458b7a05db7/skills/eval-driven-dev/SKILL.md Pinned version: install the code at commit 82701c24b99488536ca399ff4789a458b7a05db7 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "eval-driven-dev". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the skill's setup.sh to install pixie-qa and start the results web server; point the agent at my Python LLM app; provide LLM API credentials — evals make real LLM calls with real costs). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 82701c2 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.