suede-ai-eval

Designs AI eval plans, failure-mode rubrics, and pass/fail test cases for LLM features.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ai-eval-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-ai-eval
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-ai-eval
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ai-eval-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI features often ship with no testable specification, leaving teams unable to judge whether LLM, RAG, agent, or classifier behavior is safe to release. This Skill turns vague AI behavior into a concrete eval plan with failure-mode rubrics, severity scoring, and mechanical ship gates. ## Core Features & Use Cases - AI-SPEC and failure-mode rubric: Defines the AI job in one paragraph, then maps failure modes with severity, likelihood, detectability, owner, and gate. - Eval case design and coverage audit: Produces concrete pass/fail cases with inputs, expected and forbidden traits, and scores coverage and infrastructure (tooling, dataset, CI, guardrails, tracing). - Mechanical ship verdict: Returns ship, ship-with-caveats, or hold based on whether severity 4-5 failure modes have cases, gates, and evidence. - Use Case: Before shipping a support-ticket triage classifier, run this Skill to write the AI-SPEC, build adversarial and regression eval cases, and get a hold verdict until the severity-5 privacy boundary is covered. ## Quick Start Use the suede-ai-eval skill to audit this AI-powered feature, define its failure modes, and design eval cases with acceptance gates.

Frequently Asked Questions about suede-ai-eval

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

FAQPage Schema
How do I write evals for an LLM feature before shipping?

Start with an AI-SPEC defining the user, inputs, outputs, and disallowed behavior, then map failure modes with severity scores and write concrete pass/fail cases per mode. This Skill walks through that workflow and returns a ship, ship-with-caveats, or hold verdict.

How do I audit existing AI eval coverage?

Compare existing tests, logs, and manual checks against a failure-mode map, marking each dimension covered, partial, or missing. The Skill scores coverage and infrastructure separately and names every uncovered high-risk behavior regardless of the numeric score.

What eval tools does it recommend for RAG and prompt testing?

It detects existing tooling first, then defaults to Arize Phoenix for tracing, RAGAS for RAG metrics, Promptfoo for prompt regression in CI, and LangSmith for LangChain pipelines. These are starting points, not a mandate to install all four.

Can LLM-as-judge scores count as eval evidence?

Only after spot-checked agreement with a human-reviewed sample. A model grading its own output is not evidence, and self-judgment without human-agreement calibration is explicitly rejected by the Skill's hard gates.

When should I not use this AI eval skill?

Do not use it to review the implementation code behind the AI surface (use suede-code) or to wire a passing suite into CI (use suede-ci-gate). It also does not replace UAT of the built feature beyond the eval suite.