New to Claude Skills? Learn how to install them →

confident-ai on GitHub

DeepEval

Free

Streamline evaluation workflows for AI applications.

Get this skill

Free · Opens the source repo

What DeepEval does

DeepEval is a comprehensive evaluation workflow designed specifically for AI agents and applications utilizing large language models (LLMs). It facilitates a structured approach to evaluating and improving AI performance through a series of defined steps. Users can instrument their applications, curate datasets, create pytest evaluation suites, and run evaluations iteratively to refine agent behavior based on performance metrics. This skill is particularly beneficial for developers and data scientists looking to enhance the reliability and effectiveness of their AI implementations.

The workflow begins with inspecting the target application and understanding its existing DeepEval usage. Users are guided through a series of intake questions to determine the necessary metrics, datasets, and evaluation shapes. DeepEval emphasizes reusing existing resources whenever possible, thereby minimizing redundancy and ensuring that evaluations are grounded in previously established benchmarks. The skill supports both single-turn and multi-turn evaluation scenarios, making it versatile for various AI applications, including chatbots and retrieval-augmented generation (RAG) systems.

DeepEval also integrates with the Confident AI reporting framework, allowing users to monitor production environments and conduct online evaluations. This integration is crucial for teams that require ongoing assessment of AI performance in real-world applications. By utilizing traced evaluations, users can gain insights into the decision-making processes of their AI agents, leading to more informed iterations and improvements.

Overall, DeepEval is an essential tool for developers and researchers focused on creating robust AI systems. Its structured evaluation process, combined with the ability to generate synthetic datasets and commit evaluation suites, empowers users to systematically address performance issues and enhance their AI applications over time.

When to use it

Use DeepEval when you need to evaluate the performance of AI agents, multi-turn chatbots, or any LLM applications, especially in production environments.

When not to use it

Avoid using DeepEval for non-AI related testing or generic pytest setups that do not involve AI evaluations.

What you can build with it

Evaluating a Chatbot

Use DeepEval to assess the performance of a multi-turn chatbot by creating a dedicated pytest evaluation suite and running iterative tests.

Improving Agent Performance

Leverage DeepEval to refine the behavior of an AI agent by analyzing evaluation results and iterating on the application based on identified failures.

Monitoring Production AI

Implement DeepEval in a production environment to continuously monitor AI performance, utilizing online evaluations and Confident AI reporting.

How to install DeepEval

View source

1. Install with the skills CLI

npx skills add confident-ai/deepeval/deepeval --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by confident-ai

DeepEval

Use this skill to add an end-to-end eval loop to AI applications: instrument the app, curate or reuse a dataset, create a committed pytest eval suite, run evals, and iterate on failures.

Prerequisites

Requires Python 3.9+ and pip install deepeval in the target project. Metrics and synthetic generation need model credentials. Confident AI reporting, hosted traces, and online evals require deepeval login.

Workflow Summary

  1. Inspect the target app and existing DeepEval usage.
  2. Ask the required intake questions.
  3. Reuse existing metrics and datasets when available.
  4. Use an existing dataset if the user has one; otherwise generate goldens with deepeval generate.
  5. Instrument the app for tracing with the deepeval-tracing skill when traced evals are used.
  6. Run deepeval test run.
  7. Iterate for the requested number of rounds, defaulting to 5.

Core Principles

  1. Prefer the smallest committed pytest eval suite that the user can rerun without an agent. Do not hide goldens or tests in throwaway scripts.
  2. Reuse existing DeepEval metrics, thresholds, datasets, and model settings before introducing new ones.
  3. Prefer traced single-turn evals when the app can be instrumented. Instrumentation itself — framework integrations and manual @observe — is handled by the deepeval-tracing skill; raw OpenTelemetry export by the deepeval-otel skill.
  4. Use deepeval generate for dataset generation. Use deepeval test run for pytest eval execution. Do not default to the raw pytest command.
  5. Keep metrics in a separate metrics.py module for committed eval suites.
  6. Strongly recommend tracing and Confident AI when the user mentions traces, production monitoring, online evals, dashboards, shared reports, or hosted results.
  7. Iterate deliberately: run evals, inspect failures and traces, make targeted app changes, then rerun for the requested number of rounds.

Required Workflow

  1. Inspect the codebase for app type and existing DeepEval usage.
    • For classification guidance, read references/choose-use-case.md.
    • Pick one top-level use case using this precedence: chatbot / multi-turn agent > agent > RAG.
    • If an app is both RAG and agentic, treat it as agent. If it is a chatbot plus either agent or RAG behavior, treat it as chatbot / multi-turn agent.
    • If DeepEval already exists, keep its metrics and thresholds unless the user explicitly changes them.
  2. Ask the intake questions before editing application code.
    • Read references/intake.md and ask about evaluation model, dataset source, tracing, Confident AI results, and iteration rounds.
  3. Choose test shape, metrics, and artifacts.
    • Read references/pytest-e2e-evals.md.
    • Read references/metrics.md.
    • Read references/artifact-contracts.md for expected file locations.
    • Use templates/test_multi_turn_e2e.py for chatbot / multi-turn agent.
    • Use templates/test_single_turn_tracing.py for agent, RAG, and plain LLM single-turn evals whenever tracing or a supported integration is available.
    • Use templates/test_single_turn_no_tracing.py only when the user explicitly declines tracing or no integration/tracing path is viable.
    • Put metric instances in templates/metrics.py or the project's existing metrics module, not inline in the eval file.
  4. Prepare the dataset.
    • For existing datasets, read references/datasets.md.
    • For synthetic data, read references/synthetic-data.md.
    • First ask whether the user already has a dataset.
    • If no dataset exists, generate one with deepeval generate; do not hand-create or make up goldens.
    • Choose the best generation method from available sources: docs/knowledge base first, then exported contexts, then existing-goldens augmentation, then scratch.
    • Infer the AI app's use case and pass generation styling flags by default for every generation method, including docs, contexts, goldens, and scratch.
    • Target about 30-50 generated goldens for a useful first eval dataset.
    • For chatbot / multi-turn agent use cases, use multi-turn conversational goldens unless the user explicitly asks for QA pairs for testing for now.
    • For local or Confident AI datasets, follow references/datasets.md.
  5. Instrument the app and choose the traced eval shape.
    • Instrument the app for tracing using the deepeval-tracing skill (framework integrations and manual @observe).
    • Read references/traced-evals.md for the traced eval shapes and span metrics.
    • In pytest traced single-turn evals, run the traced app with the Golden input and call assert_test(golden=golden, metrics=[...]).
    • In script-based traced single-turn evals, use for golden in dataset.evals_iterator(metrics=[...]).
    • Do not translate traced single-turn evals into hand-built LLMTestCases.
    • Add component/span-level metrics only where diagnostics are useful.
  6. Create the pytest eval suite.
    • Read references/pytest-e2e-evals.md.
    • Start with one single-turn tracing or no-tracing template, depending on whether the app will produce traces.
    • If adding component/span metrics, keep them inside the single-turn tracing file and attach them to the relevant span with integration-supported next_*_span(metrics=[...]) or @observe(metrics=[...]).
    • Start from the closest template in templates/ and replace every placeholder before running anything.
  7. Run and iterate.
    • Use deepeval test run tests/evals/test_<app>.py.
    • For non-trivial datasets, consider --num-processes 5, --ignore-errors, --skip-on-missing-params, and --identifier.
    • Follow references/iteration-loop.md for the requested number of rounds.

Common Commands

Bootstrap single-turn goldens from docs only when no curated dataset exists:

deepeval generate --method docs --variation single-turn --documents ./docs --output-dir ./tests/evals --file-name .dataset

Run the eval suite:

deepeval test run tests/evals/test_<app>.py --num-processes 5 --identifier "iterating-on-<purpose>-round-1"

Open the latest hosted report when Confident AI is enabled:

deepeval view

References

TopicFile
Intake questions and branchingreferences/intake.md
Use case selectionreferences/choose-use-case.md
Dataset loadingreferences/datasets.md
Synthetic data generationreferences/synthetic-data.md
Metricsreferences/metrics.md
Pytest E2E evalsreferences/pytest-e2e-evals.md
Traced evals and span metricsreferences/traced-evals.md
Confident AIreferences/confident-ai.md
Dataset and eval artifact contractsreferences/artifact-contracts.md
Iteration loopreferences/iteration-loop.md

Templates

App typeTemplate
Single-turn tracingtemplates/test_single_turn_tracing.py
Single-turn no tracingtemplates/test_single_turn_no_tracing.py
Multi-turn E2Etemplates/test_multi_turn_e2e.py
Shared metric liststemplates/metrics.py

Frequently asked questions about DeepEval

Similar skills