duckdb-sql

Identify and resolve DuckDB-specific SQL differences from PostgreSQL and MySQL syntax.

475|25|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill duckdb-sql-signalpilot-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: duckdb-sql
Source: https://github.com/SignalPilot-Labs/SignalPilot/tree/main/benchmark/signalpilot-plugin/skills/duckdb-sql
Command: npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill duckdb-sql-signalpilot-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DuckDB users often encounter dialect differences compared to PostgreSQL and MySQL, leading to errors and slower development.

Core Features & Use Cases

  • Gotcha awareness: Highlights integer division, date parsing, interval syntax, and other DuckDB-specific quirks.
  • Guided porting: Helps port queries from PostgreSQL/MySQL to DuckDB with minimal changes.
  • Use Case: Analyze a dataset with date columns and ensure correct truncation and casting.

Quick Start

Use this guide to write DuckDB-compatible SQL and avoid common gotchas.

Frequently Asked Questions about duckdb-sql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I port PostgreSQL queries to DuckDB without syntax errors?

Porting PostgreSQL queries to DuckDB requires adjusting integer division, date parsing, and interval syntax to avoid common dialect errors. This Skill guides query translation with clear examples to ensure accurate type casting and minimize manual debugging.

Why does date parsing fail when moving MySQL SQL to DuckDB?

Date parsing fails in DuckDB due to specific interval syntax and truncation differences compared to MySQL. This Skill identifies these dialect gotchas and provides practical examples to correct date column casting during data modeling.

What are common DuckDB SQL gotchas with window functions and type casting?

DuckDB SQL gotchas involve distinct window function behaviors and strict type casting requirements. This Skill highlights these specific quirks to resolve query development errors and ensure accurate ETL pipeline execution.

Does DuckDB handle integer division differently than PostgreSQL?

DuckDB handles integer division differently than PostgreSQL, which commonly causes unexpected query results. This Skill identifies these specific dialect differences and provides guidance to correct syntax for accurate ETL pipelines.

What is the best way to resolve DuckDB interval syntax errors in ETL pipelines?

Resolving DuckDB interval syntax errors requires adjusting PostgreSQL or MySQL queries to match DuckDB-specific expectations. This Skill provides guided porting steps to fix date parsing and truncation issues across your ETL pipelines.