/write-query - Write Optimized SQL
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Write a SQL query from a natural language description, optimized for your specific SQL dialect and following best practices.
Usage
/write-query <description of what data you need>
Workflow
1. Understand the Request
Parse the user's description to identify:
- Output columns: What fields should the result include?
- Filters: What conditions limit the data (time ranges, segments, statuses)?
- Aggregations: Are there GROUP BY operations, counts, sums, averages?
- Joins: Does this require combining multiple tables?
- Ordering: How should results be sorted?
- Limits: Is there a top-N or sample requirement?
2. Determine SQL Dialect
If the user's SQL dialect is not already known, ask which they use:
- PostgreSQL (including Aurora, RDS, Supabase, Neon)
- Snowflake
- BigQuery (Google Cloud)
- Redshift (Amazon)
- Databricks SQL
- MySQL (including Aurora MySQL, PlanetScale)
- SQL Server (Microsoft)
- DuckDB
- SQLite
- Other (ask for specifics)
Remember the dialect for future queries in the same session.
3. Discover Schema (If Warehouse Connected)
If a data warehouse MCP server is connected:
- Search for relevant tables based on the user's description
- Inspect column names, types, and relationships
- Check for partitioning or clustering keys that affect performance
- Look for pre-built views or materialized views that might simplify the query
4. Write the Query
Follow these best practices:
Structure:
- Use CTEs (WITH clauses) for readability when queries have multiple logical steps
- One CTE per logical transformation or data source
- Name CTEs descriptively (e.g.,
daily_signups, active_users, revenue_by_product)
Performance:
- Never use
SELECT * in production queries -- specify only needed columns
- Filter early (push WHERE clauses as close to the base tables as possible)
- Use partition filters when available (especially date partitions)
- Prefer
EXISTS over IN for subqueries with large result sets
- Use appropriate JOIN types (don't use LEFT JOIN when INNER JOIN is correct)
- Avoid correlated subqueries when a JOIN or window function works
- Be mindful of exploding joins (many-to-many)
Readability:
- Add comments explaining the "why" for non-obvious logic
- Use consistent indentation and formatting
- Alias tables with meaningful short names (not just
a, b, c)
- Put each major clause on its own line
Dialect-specific optimizations:
- Apply dialect-specific syntax and functions (see
sql-queries skill for details)
- Use dialect-appropriate date functions, string functions, and window syntax
- Note any dialect-specific performance features (e.g., Snowflake clustering, BigQuery partitioning)
5. Present the Query
Provide:
- The complete query in a SQL code block with syntax highlighting
- Brief explanation of what each CTE or section does
- Performance notes if relevant (expected cost, partition usage, potential bottlenecks)
- Modification suggestions -- how to adjust for common variations (different time range, different granularity, additional filters)
6. Offer to Execute
If a data warehouse is connected, offer to run the query and analyze the results. If the user wants to run it themselves, the query is ready to copy-paste.
Examples
Simple aggregation:
/write-query Count of orders by status for the last 30 days
Complex analysis:
/write-query Cohort retention analysis -- group users by their signup month, then show what percentage are still active (had at least one event) at 1, 3, 6, and 12 months after signup
Performance-critical:
/write-query We have a 500M row events table partitioned by date. Find the top 100 users by event count in the last 7 days with their most recent event type.
Tips
- Mention your SQL dialect upfront to get the right syntax immediately
- If you know the table names, include them -- otherwise Claude will help you find them
- Specify if you need the query to be idempotent (safe to re-run) or one-time
- For recurring queries, mention if it should be parameterized for date ranges
1---2name: write-query3description: Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.4---5
6# /write-query - Write Optimized SQL
7
8> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
9
10Write a SQL query from a natural language description, optimized for your specific SQL dialect and following best practices.
11
12## Usage
13
14```
15/write-query <description of what data you need>
16```
17
18## Workflow
19
20### 1. Understand the Request
21
22Parse the user's description to identify:
23
24- **Output columns**: What fields should the result include?
25- **Filters**: What conditions limit the data (time ranges, segments, statuses)?
26- **Aggregations**: Are there GROUP BY operations, counts, sums, averages?
27- **Joins**: Does this require combining multiple tables?
28- **Ordering**: How should results be sorted?
29- **Limits**: Is there a top-N or sample requirement?
30
31### 2. Determine SQL Dialect
32
33If the user's SQL dialect is not already known, ask which they use:
34
35- **PostgreSQL** (including Aurora, RDS, Supabase, Neon)
36- **Snowflake**
37- **BigQuery** (Google Cloud)
38- **Redshift** (Amazon)
39- **Databricks SQL**
40- **MySQL** (including Aurora MySQL, PlanetScale)
41- **SQL Server** (Microsoft)
42- **DuckDB**
43- **SQLite**
44- **Other** (ask for specifics)
45
46Remember the dialect for future queries in the same session.
47
48### 3. Discover Schema (If Warehouse Connected)
49
50If a data warehouse MCP server is connected:
51
521. Search for relevant tables based on the user's description
532. Inspect column names, types, and relationships
543. Check for partitioning or clustering keys that affect performance
554. Look for pre-built views or materialized views that might simplify the query
56
57### 4. Write the Query
58
59Follow these best practices:
60
61**Structure:**
62- Use CTEs (WITH clauses) for readability when queries have multiple logical steps
63- One CTE per logical transformation or data source
64- Name CTEs descriptively (e.g., `daily_signups`, `active_users`, `revenue_by_product`)
65
66**Performance:**
67- Never use `SELECT *` in production queries -- specify only needed columns
68- Filter early (push WHERE clauses as close to the base tables as possible)
69- Use partition filters when available (especially date partitions)
70- Prefer `EXISTS` over `IN` for subqueries with large result sets
71- Use appropriate JOIN types (don't use LEFT JOIN when INNER JOIN is correct)
72- Avoid correlated subqueries when a JOIN or window function works
73- Be mindful of exploding joins (many-to-many)
74
75**Readability:**
76- Add comments explaining the "why" for non-obvious logic
77- Use consistent indentation and formatting
78- Alias tables with meaningful short names (not just `a`, `b`, `c`)
79- Put each major clause on its own line
80
81**Dialect-specific optimizations:**
82- Apply dialect-specific syntax and functions (see `sql-queries` skill for details)
83- Use dialect-appropriate date functions, string functions, and window syntax
84- Note any dialect-specific performance features (e.g., Snowflake clustering, BigQuery partitioning)
85
86### 5. Present the Query
87
88Provide:
89
901. **The complete query** in a SQL code block with syntax highlighting
912. **Brief explanation** of what each CTE or section does
923. **Performance notes** if relevant (expected cost, partition usage, potential bottlenecks)
934. **Modification suggestions** -- how to adjust for common variations (different time range, different granularity, additional filters)
94
95### 6. Offer to Execute
96
97If a data warehouse is connected, offer to run the query and analyze the results. If the user wants to run it themselves, the query is ready to copy-paste.
98
99## Examples
100
101**Simple aggregation:**
102```
103/write-query Count of orders by status for the last 30 days
104```
105
106**Complex analysis:**
107```
108/write-query Cohort retention analysis -- group users by their signup month, then show what percentage are still active (had at least one event) at 1, 3, 6, and 12 months after signup
109```
110
111**Performance-critical:**
112```
113/write-query We have a 500M row events table partitioned by date. Find the top 100 users by event count in the last 7 days with their most recent event type.
114```
115
116## Tips
117
118- Mention your SQL dialect upfront to get the right syntax immediately
119- If you know the table names, include them -- otherwise Claude will help you find them
120- Specify if you need the query to be idempotent (safe to re-run) or one-time
121- For recurring queries, mention if it should be parameterized for date ranges
anthropics