## TL;DR

Use vulnerability_scan for exploration and generate_suite when you want to review or version the scenarios before running.

## Steps

1. Write the Giskard scan description carefully, since every test case derives from it. Use vulnerability_scan for exploration and generate_suite when you want to review or version the scenarios before running. Remember the judge is an LLM, so verdicts are judgments, not exact matches.

## When to use

You are seeing this: Write the Giskard scan description carefully, since every test case derives from it. Use this skill when you run into "Giskard scan: the description drives every test, judge is an LLM not a match".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Edge cases

- Remember the judge is an LLM, so verdicts are judgments, not exact matches.
