Query Hex (Atomic)

Single responsibility: execute a Hex query via MCP, poll for completion, and return results matched against the caller-provided pattern. Hex Threads take a few minutes to run — this skill owns the full create → poll → extract cycle.

Input

Receive all three from the calling core skill:

• query — the complete, self-contained prompt to send to Hex (see Prompt Construction below)
• pattern — what the target data looks like (field names, expected shape — provided by caller; do not assume)
• context — any identifying context for the query (e.g. account name, entity ID, time range)

Prompt Construction (Critical — Read Before Creating a Thread)

Hex's Threads Agent decides which tables to query and what SQL to run based entirely on your prompt. A vague prompt causes broad table exploration and significantly slower responses. A precise prompt can shave several minutes off query time.

Rules

1. Batch everything into one prompt. Include every metric and data point the caller needs in a single create_thread call. Do NOT use continue_thread to fetch additional fields — each call re-triggers the full agent pipeline and adds multiple minutes of latency. Treat continue_thread as a last resort only when a genuinely requested data point is absent from the initial response.