CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/deepeval-evaluation

Use for any question or task about testing an LLM or RAG app with pytest, including hallucination checks in CI and answers that invent facts missing from the retrieved documents: DeepEval LLMTestCase, built-in metrics such as G-Eval, answer relevancy, faithfulness, contextual recall and precision, hallucination, bias and toxicity, deepeval test run with assert_test, and the Confident AI dashboard.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted, highly actionable skill body: executable code at every step, a useful metric catalog table, unusually strong guidance on golden-set design and judge-score stability, and a tight anti-patterns table. The main improvement levers are trimming the repeated 'Per [source]' attribution framing and moving the multi-turn section (or metric catalog) into a reference file to slim the main body.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — terse field tables, an executable quickstart, no basic-concept explanations — but the constant 'Per [de-gh][de-gh]' citation framing and verbatim vendor quotes ('Confident AI will generate testing reports...') add tokens that could be trimmed. It is above the midpoint because the padding is peripheral, not structural; below 5 because those repeated attribution phrases appear in nearly every section.

4 / 5

Actionability

Fully executable throughout: pip install and deepeval login commands, a copy-paste quickstart test, a complete GEval declines-metric example with a pinned JUDGE_MODEL constant, the evaluate() batch call, a full multi-turn ConversationalTestCase/Turn example, and a CI command with --workers. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Steps 1–7 form a clear, logical sequence (install → first test → fields → golden set → metrics → custom → batch → multi-turn → CI) with validation guidance present ('run the borderline cases several times and look at the score range', 'Pin the judge on every metric', thresholds set outside the noise band). It is not a 5 because these checkpoints are advisory prose rather than an explicit validate-fix-retry loop in the main workflow.

4 / 5

Progressive Disclosure

The single-file bundle has no nested references, clear section headers, and one-level-deep link references with a dedicated References section. Scored against the actual (empty) bundle structure, the metric catalog and the multi-turn section are the only content arguably large enough to split into reference files — a minor organization gap, so 4 rather than 5; well above 3 since navigation is easy and nothing is buried.

4 / 5

Total

17

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use for...' trigger clause, concrete natural-language trigger phrases (hallucination checks in CI, answers that invent facts), and comprehensive enumeration of the tool's capabilities. The only weaknesses are a few missing common synonyms ('evals', 'LLM-as-judge') and mild overlap risk with sister LLM-evaluation skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities: 'DeepEval LLMTestCase, built-in metrics such as G-Eval, answer relevancy, faithfulness, contextual recall and precision, hallucination, bias and toxicity, deepeval test run with assert_test, and the Confident AI dashboard' — comprehensive and specific, matching the top anchor. It is not a 4 because coverage of the tool's surface is near-complete rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both: 'Use for any question or task about testing an LLM or RAG app with pytest' gives the when with concrete trigger situations, and the enumerated metrics/commands give the what. Not a 4 because both halves are explicit rather than the 'when' being merely adequate.

5 / 5

Trigger Term Quality

Natural phrases like 'testing an LLM or RAG app with pytest', 'hallucination checks in CI', and 'answers that invent facts missing from the retrieved documents' match how users would phrase the need, plus tool-specific terms (G-Eval, faithfulness). It falls short of 5 because common variants such as 'evals', 'LLM-as-judge', or 'regression testing' are absent.

4 / 5

Distinctiveness Conflict Risk

DeepEval-specific terms (LLMTestCase, assert_test, Confident AI dashboard) establish a clear niche with distinct triggers, but the broad 'testing an LLM or RAG app' framing overlaps with sibling eval skills like promptfoo or ragas. Not a 5 due to that residual overlap risk with closely related evaluation tools; well above a 3 since the tool-specific vocabulary disambiguates most cases.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page