install-duckdb
by duckdbinstall-duckdb helps install or update DuckDB extensions from the CLI. Use plain extension names for core installs, or name@repo for repository-based extensions. The skill checks for DuckDB first, handles --update separately, and turns a simple request into valid DuckDB INSTALL commands with less guesswork.
This skill scores 78/100, which means it is a solid directory candidate with real installation value for DuckDB users. Directory users can expect a triggerable workflow for installing or updating extensions, but should note that the repo is more operational than explanatory and leaves some edge-case handling implicit.
- Explicit trigger and argument contract for install vs. update, including plain names and name@repo syntax.
- Concrete Bash-based workflow that finds the DuckDB CLI, constructs INSTALL statements, and stops early if DuckDB is missing.
- Repository includes an eval.sh that exercises the skill end-to-end and checks extensions are loadable, which improves trustworthiness.
- SKILL.md is somewhat terse: description length is minimal and there is no standalone install command or broader usage guide.
- Update-path details are only partially visible in the excerpt, so users may still need to inspect the skill for full behavior and limits.
Overview of install-duckdb skill
What install-duckdb does
The install-duckdb skill installs or updates DuckDB extensions from the CLI. It is built for people who want a reliable install-duckdb install flow instead of writing ad hoc INSTALL statements by hand. The skill accepts plain extension names for core extensions and name@repo pairs for extensions hosted in a repository.
Who should use it
Use this install-duckdb skill if you already work in DuckDB and need to add extensions quickly, repeatably, and with less syntax guessing. It is most useful for agents or users who need a short, execution-ready path from a rough request like “install spatial and a community extension” to valid DuckDB commands.
What makes it different
The main value of install-duckdb for Skill Installation is that it translates a small input list into the right DuckDB INSTALL form and handles the --update path separately. That makes the skill practical for both first-time installs and maintenance workflows. It also checks for DuckDB CLI availability first, which prevents a confusing failure later in the process.
How to Use install-duckdb skill
Install the skill and confirm DuckDB
For the install-duckdb install, load the skill through your GitHub skill workflow, then make sure duckdb is on your PATH before you ask it to do anything. If DuckDB is missing, the skill is designed to stop and tell you to install the CLI first. That matters because the skill is not a package manager; it is a DuckDB-aware installer wrapper.
Give the skill clean extension input
The best install-duckdb usage starts with names the skill can parse directly:
spatialftsmagic@community
Use plain names when you want DuckDB’s core repository. Use name@repo when the extension comes from a non-default repo. If you want an update, include --update and only the extension targets you actually want touched.
Read the repo in the right order
For install-duckdb guide work, start with SKILL.md to understand the argument rules and execution flow. Then inspect eval.sh to see how the maintainers validate behavior in practice. That file is especially useful if you want to understand what “success” looks like after installation and how the skill is expected to behave under automation.
Turn a rough request into a better prompt
Stronger prompts reduce ambiguity. Instead of “install DuckDB extensions,” say:
/duckdb-skills:install-duckdb spatial fts
or
/duckdb-skills:install-duckdb --update magic@community
Include only the extensions you want, name any non-core repo explicitly, and avoid mixing unrelated tasks into the same request. The skill works best when the prompt is specific enough that the generated DuckDB statements are obvious.
install-duckdb skill FAQ
Is install-duckdb only for installation?
No. The install-duckdb skill also supports updating extensions, which is useful when you need to refresh an existing setup rather than add something new. That update path is part of what makes the skill more useful than a one-off prompt.
Do I need DuckDB installed first?
Yes. The skill checks for the DuckDB CLI and stops if it cannot find it. If you are evaluating install-duckdb for Skill Installation, that prerequisite is a real adoption gate, not a minor detail.
When should I not use this skill?
Do not use it if you are trying to manage unrelated system packages, Python dependencies, or database migrations. This skill is narrowly focused on DuckDB extension installation and update behavior. If your goal is broader environment setup, a generic prompt or a different skill is a better fit.
Is it beginner-friendly?
Yes, if the user can name the extensions they want. The skill hides DuckDB syntax details, but it still expects the user to know whether an extension is core or comes from another repo. Beginners do best when they provide the extension names exactly as they appear in DuckDB documentation or release notes.
How to Improve install-duckdb skill
Specify the exact extension targets
The biggest quality gain comes from better extension lists. If you want install-duckdb usage to succeed on the first pass, name each target clearly and include @repo only when needed. Vague requests like “install the useful extensions” force guesswork and weaken the output.
Separate install and update intent
A common failure mode is mixing “install this” with “update everything” in one request. The install-duckdb skill handles those cases differently, so be explicit about the mode you want. If you are updating, say so up front and list only the extensions that matter.
Verify the result after the first run
For higher confidence, validate that the extension loads in DuckDB after the skill runs. That is the real test of a successful install-duckdb install, not just whether a command was printed. If one extension fails to load, refine the input by checking the repo source, extension spelling, and whether the extension should come from core or a specific repo.