## TL;DR

Run any command with --debug (or -d) for verbose logs covering the environment, the command, and network interactions with the Snyk API.

## Steps

1. Per Snyk docs: --debug plus SNYK_LOG_LEVEL=trace gives full API-level tracing of CLI behavior.

## When to use

You are seeing this: Per Snyk docs: --debug plus SNYK_LOG_LEVEL=trace gives full API-level tracing of CLI behavior. Use this skill when you run into "Debugging the Snyk CLI with --debug and SNYK_LOG_LEVEL set to trace".

## 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.
