Menú
Strict rules on outputting ClickHouse syntax, limiting rows, and rendering SQL in markdown.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Rules and strategies for exploring databases, tables, schemas, and searching metadata.
Complex rules for calling render_chart, inferring axes, and choosing chart types based on user intent.
Diagnose a ClickHouse server error (code/name/exception) and give a concrete, actionable fix.
Diagnose part/partition health of a MergeTree table — too many parts, slow/stuck merges, bad partition key.
Rules for using explain/analyze/optimize tools to help the user tune their queries.
Diagnose a column/table schema issue — Nullable overhead, oversized integer, or weak compression — and propose an ALTER.
| name | sql-generation |
| description | Strict rules on outputting ClickHouse syntax, limiting rows, and rendering SQL in markdown. |
The user wants a SQL query written and/or executed, validated without running, or its results exported. Gather schema first (data-exploration) if table/column names aren't already confirmed.
get_table_schema / search_columns — confirm real column names first.run_select_query — execute the SELECT and show results.validate_sql — when the user wants to check a query WITHOUT running it.export_query_result — when the user wants results as CSV/JSON.SELECT / WITH queries — READ-ONLY access.LIMIT 100 unless the user asks for a different limit.SELECT *.FORMAT clause — the app formats output itself.run_select_query fails on permissions, report the error accurately.