Agent skill

Lance Duckdb Update Lance Dependency

by lance-format in lance-format/lance-duckdb

Update lance-duckdb to a specific Lance release or tag. An agent skill from lance-format/lance-duckdb.

Apache-2.0Auto-check passedDevelopment

Install Lance Duckdb Update Lance Dependency

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .claude/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .claude/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .agents/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .agents/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .cursor/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .cursor/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/lance-format/lance-duckdb.git --path .agents/skills/lance-duckdb-update-lance-dependency

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .gemini/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .gemini/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .github/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .github/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install lance-format/lance-duckdb lance-duckdb-update-lance-dependency --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lance-format/lance-duckdb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/lance-duckdb-update-lance-dependency .opencode/skills/lance-duckdb-update-lance-dependency && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "lance-duckdb-update-lance-dependency" agent skill from https://github.com/lance-format/lance-duckdb/tree/main/.agents/skills/lance-duckdb-update-lance-dependency into .opencode/skills/lance-duckdb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lance-duckdb-update-lance-dependency", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: lance-duckdb-update-lance-dependency
GitHub stars: 129
Token cost: ~1k tokens
SKILL.md length: 440 words
Files: 1
Skills in repo: 1
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Update lance-duckdb to a specific Lance release or tag. An agent skill from lance-format/lance-duckdb.

Works in 11 steps: Confirm the worktree status with git… → Resolve the target Lance version → Compute update metadata without changing… → …
Bumping Lance Rust dependencies in the lance-duckdb repository
SKILL.md covers Scope, Workflow and GitHub Actions
Calls python3, gh and cargo; needs GH_TOKEN and GITHUB_TOKEN

What it does

Lance Duckdb Update Lance Dependency is an agent skill from lance-format/lance-duckdb. Update lance-duckdb to a specific Lance release or tag. Use when bumping Lance Rust dependencies in the lance-duckdb repository, including Cargo.toml, Cargo.lock, validation, branch creation, commit, push, and PR creation when requested.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with DuckDB, Rust and Git. The repository describes itself as: The lance extensions for DuckDB enable reading and writing of lance tables. The licence is Apache-2.0.

When your agent uses it

Bumping Lance Rust dependencies in the lance-duckdb repository
Including Cargo.toml
Branch creation
PR creation when requested

Example prompts

“/lance-duckdb-update-lance-dependency”

Requirements

Python 3
A credential in GITHUB_TOKEN

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

Confirm the worktree status with git status --short.
Resolve the target Lance version
Compute update metadata without changing files
Run the deterministic update entrypoint
Run validation
Inspect git status --short and git diff to ensure only the Lance dependency update and required compatibility fixes are present.
If the task only asks to prepare local changes, stop here and report the changed files and validation result.
If the task asks to publish the update, create a branch using the printed branch_name, stage all relevant files, and commit using the…
Push to origin. Before creating the PR, check that the current token has push permission
Create a PR targeting main with the printed pr_title. If there is no PR template, keep the body to two or three concise sentences: state…
Read back the remote PR title after creation. If it is not a Conventional Commit title, fix it immediately.

What it can do on your machine

Read from SKILL.md and the folder at commit c886612. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
- gh
- cargo
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GH_TOKEN
- GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lance Duckdb Update Lance Dependency loads about 1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from lance-format/lance-duckdb at commit c886612, republished under its Apache-2.0 licence (© lance-format). 440 words, ~1,002 tokens.

Download SKILL.mdSave it as .claude/skills/lance-duckdb-update-lance-dependency/SKILL.md (or your agent's skills folder).

name: lance-duckdb-update-lance-dependency
description: Update lance-duckdb to a specific Lance release or tag. Use when bumping Lance Rust dependencies in the lance-duckdb repository, including Cargo.toml, Cargo.lock, validation, branch creation, commit, push, and PR creation when requested.

lance-duckdb Update Lance Dependency

Scope

Use this skill in the lance-format/lance-duckdb repository when updating Lance Rust dependencies to a specific Lance version or tag.

Inputs can be a version (7.2.0-beta.1), a tag (v7.2.0-beta.1), a tag ref (refs/tags/v7.2.0-beta.1), or latest.

Workflow

Confirm the worktree status with git status --short.
Resolve the target Lance version:
- If the input is latest, empty, or omitted, run:
  bash
```
python3 ci/check_lance_release.py
```
  Parse the JSON output. If needs_update is not true, stop without creating a PR. Otherwise use latest_tag.
- If the input is explicit, use it directly.
Compute update metadata without changing files:
bash
```
python3 ci/update_lance_dependency.py "$TAG_OR_VERSION" --metadata-only
```
Before making changes, check for an existing open PR with the emitted pr_title:
bash
```
gh pr list --search "\"$PR_TITLE\" in:title" --state open --limit 1 --json number,url,title
```
If a matching open PR exists, stop and report it instead of creating a duplicate.
Run the deterministic update entrypoint:
bash
```
python3 ci/update_lance_dependency.py "$TAG_OR_VERSION"
```
This updates the direct Lance Rust crate versions in Cargo.toml, removes repository-local Lance [patch.crates-io] entries if present, refreshes Cargo.lock with precise Cargo updates, and prints JSON metadata containing branch_name, commit_message, and pr_title.
Run validation:
bash
```
cargo fmt --all
cargo check --manifest-path Cargo.toml
cargo clippy --manifest-path Cargo.toml --all-targets
```
If Cargo reports incompatible Arrow/DataFusion requirements, inspect the target Lance release requirements and update the pinned Arrow/DataFusion versions in Cargo.toml, then rerun python3 ci/update_lance_dependency.py "$TAG_OR_VERSION" and the validation commands. Fix real diagnostics and rerun validation until it succeeds.
Inspect git status --short and git diff to ensure only the Lance dependency update and required compatibility fixes are present.
If the task only asks to prepare local changes, stop here and report the changed files and validation result.
If the task asks to publish the update, create a branch using the printed branch_name, stage all relevant files, and commit using the printed commit_message. Do not amend or rewrite existing commits.
Push to origin. Before creating the PR, check that the current token has push permission:
bash
```
gh api repos/lance-format/lance-duckdb --jq .permissions.push
```
If the remote branch already exists for the same generated branch name, delete the remote ref with gh api -X DELETE repos/lance-format/lance-duckdb/git/refs/heads/$BRANCH_NAME, then push. Do not force-push.
Create a PR targeting main with the printed pr_title. If there is no PR template, keep the body to two or three concise sentences: state the Lance dependency bump, note any required compatibility fixes, and link the triggering Lance tag or release.
Read back the remote PR title after creation. If it is not a Conventional Commit title, fix it immediately.

Show full SKILL.md (54 more words)Show less

GitHub Actions

This workflow is intentionally manual. When this skill is used from GitHub Actions, TAG, GH_TOKEN, and GITHUB_TOKEN may already be set. Resolve latest first when TAG is empty. Once an explicit tag or version is known, use:

bash

python3 ci/update_lance_dependency.py "$TAG" --github-output "$GITHUB_OUTPUT"

Then use the emitted branch_name, commit_message, and pr_title values for branch, commit, and PR creation.

Files

Just SKILL.md in .agents/skills/lance-duckdb-update-lance-dependency of lance-format/lance-duckdb.

Open the folder on GitHubat commit c886612

Compare with similar skills

Lance Duckdb Update Lance Dependency next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lance Duckdb Update Lance Dependency compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Lance Duckdb Update Lance Dependency this skilllance-format/lance-duckdb	129	—	~1k	Automated safety check: Pass	Apache-2.0	6 days ago
Worktrunk Tend CI Guidancemax-sixty/worktrunk	9k	—	~6.4k	Automated safety check: Pass	Custom licence	today
Worktrunk Release Workflowmax-sixty/worktrunk	9k	—	~6.9k	Automated safety check: Pass	Custom licence	today
RustPython Stdlib UpgradeRustPython/RustPython	22k	—	~876	Automated safety check: Pass	MIT	today
BrDicklesworthstone/beads_rust	1.1k	—	~2.7k	Automated safety check: Pass	MIT	today
Debug Tuitrasta298/keifu	811	—	~1.3k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Worktrunk Tend CI Guidance
max-sixty/worktrunk
Adds Worktrunk-specific rules to the tend CI workflows: Codecov polling, Rust test commands, labels and review criteria for pull requests handled in CI.
9k GitHub stars~6.4k tokensUpdated today
DevelopmentAuto-check passed
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
9k GitHub stars~6.9k tokensUpdated today
DevelopmentAuto-check passed
RustPython Stdlib Upgrade
RustPython/RustPython
Upgrades a Python standard library module from CPython into RustPython with update_lib, then triages and marks the tests that still fail.
22k GitHub stars~876 tokensUpdated today
DevelopmentAuto-check passed
Br
Dicklesworthstone/beads_rust
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
1.1k GitHub stars~2.7k tokensUpdated today
DevelopmentAuto-check passed
Debug Tui
trasta298/keifu
Drive and debug the real keifu TUI autonomously via its remote-control debug server (--debug-listen) — launch headlessly, inject keys/mouse, dump the rendered screen as text, and inspect app state.
811 GitHub stars~1.3k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Worktrunk CLI Output Rules
max-sixty/worktrunk
CLI output standards for worktrunk: message functions, ANSI color nesting and the shell integration that changes directory after the wt command exits.
9k GitHub stars~12k tokensUpdated today
DevelopmentAuto-check passed

Works with

Questions about Lance Duckdb Update Lance Dependency

What does Lance Duckdb Update Lance Dependency do?

Update lance-duckdb to a specific Lance release or tag. An agent skill from lance-format/lance-duckdb. Lance Duckdb Update Lance Dependency is an agent skill from lance-format/lance-duckdb. Update lance-duckdb to a specific Lance release or tag.

When should I use Lance Duckdb Update Lance Dependency?

Lance Duckdb Update Lance Dependency fits situations like: bumping Lance Rust dependencies in the lance-duckdb repository; including Cargo.toml; branch creation; PR creation when requested.

How do I install Lance Duckdb Update Lance Dependency in Claude Code?

Run `npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a claude-code`. Or copy the skill folder (.agents/skills/lance-duckdb-update-lance-dependency in lance-format/lance-duckdb) into .claude/skills/lance-duckdb-update-lance-dependency in your project. Claude Code loads it when a task matches its description.

How do I install Lance Duckdb Update Lance Dependency in Codex?

Run `npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a codex`. Or copy the skill folder (.agents/skills/lance-duckdb-update-lance-dependency in lance-format/lance-duckdb) into .agents/skills/lance-duckdb-update-lance-dependency in your project. Codex loads it when a task matches its description.

Can I use Lance Duckdb Update Lance Dependency in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lance-format/lance-duckdb --skill lance-duckdb-update-lance-dependency -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lance-duckdb-update-lance-dependency, .gemini/skills/lance-duckdb-update-lance-dependency, .github/skills/lance-duckdb-update-lance-dependency and .opencode/skills/lance-duckdb-update-lance-dependency in your project.

What does Lance Duckdb Update Lance Dependency need to run?

Going by SKILL.md and its folder, Lance Duckdb Update Lance Dependency needs the command-line tools its instructions call (python3, gh, cargo and git) and credentials named GH_TOKEN and GITHUB_TOKEN. Our summary lists: Python 3; A credential in GITHUB_TOKEN.

Does Lance Duckdb Update Lance Dependency access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Lance Duckdb Update Lance Dependency safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lance Duckdb Update Lance Dependency use?

Lance Duckdb Update Lance Dependency is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lance Duckdb Update Lance Dependency use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lance Duckdb Update Lance Dependency?

Skills that share tags, products or a category with Lance Duckdb Update Lance Dependency: Worktrunk Tend CI Guidance (max-sixty/worktrunk, 9k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), RustPython Stdlib Upgrade (RustPython/RustPython, 22k stars) and Br (Dicklesworthstone/beads_rust, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lance Duckdb Update Lance Dependency?

lance-format (a GitHub organization) maintains it in lance-format/lance-duckdb, which has 129 GitHub stars. The repository was last updated on October 2, 2026.

Source: lance-format/lance-duckdb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Lance Duckdb Update Lance Dependency

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

lance-duckdb Update Lance Dependency

Scope

Workflow

GitHub Actions

Files

Compare with similar skills

Similar skills

Worktrunk Tend CI Guidance

Worktrunk Release Workflow

RustPython Stdlib Upgrade

Br

Debug Tui

Worktrunk CLI Output Rules

Related

Questions about Lance Duckdb Update Lance Dependency