メニュー
Search DuckDB and DuckLake documentation via full-text search. Use when encountering DuckDB errors, looking up function syntax, or when other skills hit unknown DuckDB behavior. Also use proactively when unsure about DuckDB features.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Build data processing pipelines using DuckDB, GDAL, and gpio as pixi tasks. Use when creating ETL workflows, multi-step data transformations, format conversions, or batch processing — even if the user just says "process this data" or "build a pipeline".
Attach a DuckDB database for persistent querying. Use when the user has a .duckdb file they want to explore, or when they want to persist query results across sessions. Explores schema and wires up state.sql so all DuckDB skills can access it.
Install or update DuckDB extensions. Use when DuckDB reports a missing extension, when the user asks to install/update extensions, or when other skills delegate here. Each argument is a plain extension name or name@repo. Pass --update to update.
Run SQL queries against DuckDB databases or ad-hoc files. Accepts raw SQL or natural language. Use whenever the user wants to query data, explore tables, run analytics, or ask questions about datasets — even if they don't say "DuckDB" explicitly.
Read and explore any data file (CSV, JSON, Parquet, Avro, Excel, spatial, remote) using DuckDB. Use proactively when the user mentions a data file, asks "what's in this file", or wants to explore/preview/describe any dataset — even without saying DuckDB.
Search past Claude Code session logs to recover context. Use proactively when recalling past decisions, patterns, or unresolved work from previous sessions.
SOC 職業分類に基づく
| name | duckdb-docs |
| description | Search DuckDB and DuckLake documentation via full-text search. Use when encountering DuckDB errors, looking up function syntax, or when other skills hit unknown DuckDB behavior. Also use proactively when unsure about DuckDB features. |
| argument-hint | <question or keyword> |
| allowed-tools | Bash |
Query: $@
| Index | URL | Cache file | Versions |
|---|---|---|---|
| DuckDB | https://duckdb.org/data/docs-search.duckdb | duckdb-docs.duckdb | stable, current, blog |
| DuckLake | https://ducklake.select/data/docs-search.duckdb | ducklake-docs.duckdb | stable, preview |
Schema: chunk_id (PK), page_title, section, breadcrumb, url, version, text
Default: search DuckDB stable. Use current for nightly, blog for background, DuckLake index for DuckLake questions.
Natural language → extract key technical terms (drop stop words). Technical terms → use as-is.
pixi run python -c "import pathlib; pathlib.Path.home().joinpath('.duckdb','docs').mkdir(parents=True, exist_ok=True)"
Check freshness (≤2 days). If stale/missing:
pixi run duckdb -c "
LOAD httpfs; LOAD fts;
ATTACH 'REMOTE_URL' AS remote (READ_ONLY);
ATTACH '$HOME/.duckdb/docs/CACHE_FILE.tmp' AS tmp;
COPY FROM DATABASE remote TO tmp;
" && mv "$HOME/.duckdb/docs/CACHE_FILE.tmp" "$HOME/.duckdb/docs/CACHE_FILE"
pixi run duckdb "$HOME/.duckdb/docs/CACHE_FILE" -readonly -json -c "
LOAD fts;
SELECT chunk_id, page_title, section, url, version, text,
fts_main_docs_chunks.match_bm25(chunk_id, 'SEARCH_QUERY') AS score
FROM docs_chunks
WHERE score IS NOT NULL AND version = 'VERSION'
ORDER BY score DESC LIMIT 8;
"
No results → broaden query, drop least specific term. Still nothing → suggest docs website.
Show results ordered by score, then synthesize a concise answer to $@.