> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidlogs/programmers/checks.md).

# Checks

**Event setup › Checks** (programmers and admins) controls the checks for the season: turn each one on or off, **Edit thresholds**, or mark it **Experimental** while it still cries wolf. Experimental findings show apart and don't count. **Reset to defaults** undoes a season's changes.

Before changing a default, replay it against real logs with `bun run replay` (see [Pit laptop tools](https://docs.raidrobotics.org/raidlogs/programmers/pit-laptop-tools.md)) and make sure it doesn't fire on healthy matches.

## Check list summary

After the checks run, a model ranks the trusted findings into the short list at the top of each report card. It never adds a problem the checks didn't find, and costs about $0.001 a match. This section shows how many lists were written this season and what they cost, and is where an admin sets the Anthropic API key.

See [What the checks look for](https://docs.raidrobotics.org/raidlogs/reference/checks.md) for the full list.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/raidlogs/programmers/checks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
