sql-queries
This Claude Code skill transforms natural language requests into optimized SQL queries across multiple database platforms including BigQuery, PostgreSQL, MySQL, and Snowflake. Use it when you need to generate accurate SQL without manual syntax work, particularly for data analysis, report building, or exploring databases. The skill reads database schemas from uploaded files and documentation to understand your table structures before generating queries with performance considerations and explanations.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/sql-queries && cp -r /tmp/sql-queries/pm-data-analytics/skills/sql-queries ~/.claude/skills/sql-queriesSKILL.md
# SQL Query Generator ## Purpose Transform natural language requirements into optimized SQL queries across multiple database platforms. This skill helps product managers, analysts, and engineers generate accurate queries without manual syntax work. ## How It Works ### Step 1: Understand Your Database Schema - If you provide a schema file (SQL, documentation, or diagram description), I will read and analyze it - Extract table names, column definitions, data types, and relationships - Identify primary keys, foreign keys, and indexing strategies ### Step 2: Process Your Request - Clarify the exact data you need to retrieve or analyze - Confirm the SQL dialect (BigQuery, PostgreSQL, MySQL, Snowflake, etc.) - Ask for any additional requirements (filters, aggregations, sorting) ### Step 3: Generate Optimized Query - Write efficient SQL that leverages your database structure - Include comments explaining complex logic - Add performance considerations for large datasets - Provide alternative approaches if applicable ### Step 4: Explain and Test - Explain the query logic in plain English - Suggest how to test or validate results - Offer tips for performance optimization - If you want, generate a test script or sample data ## Usage Examples **Example 1: Query from Schema File** ``` Upload your database_schema.sql file and say: "Generate a query to find users who signed up in the last 30 days and had at least 5 active sessions" ``` **Example 2: Query from Diagram Description** ``` "Here's my database: Users table (id, email, created_at), Sessions table (id, user_id, timestamp, duration). Generate a query for average session duration per user in January 2026." ``` **Example 3: Complex Analysis Query** ``` "Create a BigQuery query to analyze our revenue by region and customer tier, including year-over-year growth rates." ``` ## Key Capabilities - **Multi-Dialect Support**: Works with BigQuery, PostgreSQL, MySQL, Snowflake, SQL Server - **File Reading**: Reads schema files, SQL dumps, and data documentation - **Query Optimization**: Suggests indexes, partitioning, and performance improvements - **Explanation**: Breaks down queries for learning and documentation - **Testing**: Can generate test queries and sample data scripts - **Script Execution**: Create executable SQL scripts for your database ## Tips for Best Results 1. **Provide context**: Share your database schema or structure 2. **Be specific**: Clearly describe what data you need and any filters 3. **Mention database**: Specify which SQL dialect you're using 4. **Include constraints**: Mention data volume, time ranges, and performance needs 5. **Request format**: Ask for the query result format if you need specific output ## Output Format You'll receive: - **SQL Query**: Production-ready SQL code with comments - **Explanation**: What the query does and how it works - **Performance Notes**: Optimization tips and considerations - **Test Script** (if requested): Sample data and validation queries --- ### Further Reading - [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr) - [How to Become a Technology-Literate PM](https://www.productcompass.pm/p/how-to-become-a-technology-literate)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.