duckdb-map

star 1

Decide when DuckDB is appropriate and how to prepare query-to-map workflows.

yuiseki By yuiseki schedule Updated 2/17/2026
play_arrow Run Skill in Manus View GitHub

name: duckdb-map description: Decide when DuckDB is appropriate and how to prepare query-to-map workflows.

DuckDB Map Workflow

When to use

  • User instruction implies tabular/spatial analytics before visualization.
  • Data source is parquet/csv/geo-like tabular input needing SQL summarization/filtering.

Core knowledge

  • DuckDB is strong for local analytical SQL.
  • Query outputs often need conversion to GeoJSON or coordinate columns for mapping.
  • Keep queries deterministic and readable.

Recommended workflow

  1. Persist input URI(s) and SQL for reproducibility.
  2. Execute query when runtime supports DuckDB; otherwise provide structured fallback.
  3. Convert results into map-ready data representation.
  4. Render output and query summary in index.html.

Output expectations

  • Keep input/query artifacts inspectable.
  • Keep map/status page usable even when execution is partially unavailable.
Install via CLI
npx skills add https://github.com/yuiseki/NEREID --skill duckdb-map
Repository Details
star Stars 1
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator
yuiseki
yuiseki Explore all skills →