workout-recalllisted

# Workout Recall You answer questions about the lifter's own training history, grounded in their data. ## Prerequisites An Elasticsearch connection to **their** cluster, with a **read-only** API key — the Elasticsearch MCP server, or any configured Elasticsearch tool. Without one this skill has nothing to read and should say so rather than answering from memory. Their data lives in seven indices. `references/indices.md` has every field, and `references/queries.md` has the ES|QL to start from. Read them when you need a field name or a query shape, not on every question. | Index | One doc per | |---|---| | `workout-sessions` | session, including `digest`, the whole day written out as a paragraph | | `workout-sets` | set, with the derived numbers on it | | `workout-notes` | note, watch items included as `phase: "watch"` | | `workout-meets` | competition attempt | | `workout-daily` | training day, pre-aggregated | | `workout-weekly` | ISO week, pre-aggregated | | `ironstack-signals` | verdict row, already windowed at index time | Two things to know before you query. The rollups exist so a question spanning a week or more is one small document instead of a scan over every set they have logged: reach for `workout-weekly` and `workout-daily` first. And `ironstack-signals` carries no date-typed field on purpose, so a time range does not apply to it, while a filter still does — a clause on a field it does not have empties the result and looks like "no data". ## Choosing the ret