Agent skill

Lancedb Update Lance Dependency

Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb.

Apache-2.0Auto-check passedDatabases

Install Lancedb Update Lance Dependency

skills CLI

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

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

GitHub CLI

$ gh skill install lancedb/lancedb lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .claude/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .claude/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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/lancedb/lancedb/tree/main/.agents/skills/lancedb-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 lancedb/lancedb --skill lancedb-update-lance-dependency -a codex

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

GitHub CLI

$ gh skill install lancedb/lancedb lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .agents/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .agents/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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 lancedb/lancedb --skill lancedb-update-lance-dependency -a cursor

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

GitHub CLI

$ gh skill install lancedb/lancedb lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .cursor/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .cursor/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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/lancedb/lancedb.git --path .agents/skills/lancedb-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 lancedb/lancedb --skill lancedb-update-lance-dependency -a gemini-cli

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

GitHub CLI

$ gh skill install lancedb/lancedb lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .gemini/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .gemini/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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 lancedb/lancedb lancedb-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 lancedb/lancedb --skill lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .github/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .github/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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 lancedb/lancedb --skill lancedb-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 lancedb/lancedb lancedb-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/lancedb/lancedb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/lancedb-update-lance-dependency .opencode/skills/lancedb-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 "lancedb-update-lance-dependency" agent skill from https://github.com/lancedb/lancedb/tree/main/.agents/skills/lancedb-update-lance-dependency into .opencode/skills/lancedb-update-lance-dependency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lancedb-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: lancedb-update-lance-dependency
GitHub stars: 12k
Token cost: ~1.1k tokens
SKILL.md length: 478 words
Files: 1
Skills in repo: 1
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb.

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

What it does

Lancedb Update Lance Dependency is an agent skill from lancedb/lancedb. Update LanceDB to a specific Lance release or tag. Use when bumping Lance dependencies in the lancedb repository, including Rust workspace Lance crates, Java lance-core, validation, branch creation, commit, push, and PR creation when requested.

Its SKILL.md is about 1.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 Databases, covering Vector databases. It works with Java, Rust and Git. The repository describes itself as: Developer-friendly OSS embedded retrieval library for multimodal AI. Search More; Manage Less. The licence is Apache-2.0.

When your agent uses it

Bumping Lance dependencies in the lancedb repository
Including Rust workspace Lance crates
Java lance-core
Branch creation

Example prompts

“/lancedb-update-lance-dependency”

Requirements

Python 3
A credential in GITHUB_TOKEN

Workflow steps

12 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.
When running in GitHub Actions after creating the LanceDB PR, trigger the Sophon dependency update

What it can do on your machine

Read from SKILL.md and the folder at commit 07e626e. 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
- git
- cargo
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

Lancedb Update Lance Dependency loads about 1.1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 478 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: ~1.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 lancedb/lancedb at commit 07e626e, republished under its Apache-2.0 licence (© lancedb). 478 words, ~1,058 tokens.

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

name: lancedb-update-lance-dependency
description: Update LanceDB to a specific Lance release or tag. Use when bumping Lance dependencies in the lancedb repository, including Rust workspace Lance crates, Java lance-core, validation, branch creation, commit, push, and PR creation when requested.

LanceDB Update Lance Dependency

Scope

Use this skill in the lancedb/lancedb repository when updating the Lance dependency 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 Rust workspace Lance dependencies through ci/set_lance_version.py, updates java/pom.xml, refreshes Cargo metadata, and prints JSON metadata containing branch_name, commit_message, and pr_title.
Run validation:
bash
```
cargo clippy --quiet --workspace --tests --all-features -- -D warnings
cargo fmt --all --quiet
```
Fix real diagnostics and rerun clippy until it succeeds. Do not skip warnings.
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/lancedb/lancedb --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/lancedb/lancedb/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.
When running in GitHub Actions after creating the LanceDB PR, trigger the Sophon dependency update:
bash
```
gh workflow run codex-bump-lancedb-lance.yml \
  --repo lancedb/sophon \
  -f lance_ref="$LANCE_TAG" \
  -f lancedb_ref="$BRANCH_NAME"
gh run list --repo lancedb/sophon --workflow codex-bump-lancedb-lance.yml --limit 1 --json databaseId,url,displayTitle
```
Use the emitted metadata tag value as LANCE_TAG. Do this only after a new LanceDB PR has been created. If the update was skipped because no update is needed or an open PR already exists, do not trigger Sophon.

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

GitHub Actions

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/lancedb-update-lance-dependency of lancedb/lancedb.

Open the folder on GitHubat commit 07e626e

Compare with similar skills

Lancedb 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.

Lancedb Update Lance Dependency compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Lancedb Update Lance Dependency this skilllancedb/lancedb	12k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Qdrant Clients SDKqdrant/skills	253	2 repos	~752	Automated safety check: Notes	Apache-2.0	yesterday
Qdrant Advisorqdrant/skills	253	—	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Check Toolsoaustegard/claude-skills	150	—	~641	Automated safety check: Pass	MIT	today
Qdrant Vector SearchOrchestra-Research/AI-Research-SKILLs	13k	5 repos	~3.4k	Automated safety check: Pass	MIT	3 mo ago
Paro Optimizerzunor/paro	105	—	~979	Automated safety check: Pass	Apache-2.0	today

Similar skills

Qdrant Clients SDK
qdrant/skills
Official
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
253 GitHub starsUsed in 2 repos~752 tokens
DatabasesAuto-check: notes
Qdrant Advisor
qdrant/skills
Official
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.
253 GitHub stars~1.7k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Check Tools
oaustegard/claude-skills
Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities.
150 GitHub stars~641 tokensUpdated today
DevelopmentAuto-check passed
Qdrant Vector Search
Orchestra-Research/AI-Research-SKILLs
Explains how to run Qdrant, a Rust vector database, for RAG and semantic search, covering collections, points, distance metrics and filtered or batched queries.
13k GitHub starsUsed in 5 repos~3.4k tokens
DatabasesAuto-check passed
Paro Optimizer
zunor/paro
Design, refactor and diagnose Paro's staged optimizer, using EXPLAIN COMPILE for planning and EXPLAIN ANALYZE for execution.
105 GitHub stars~979 tokensUpdated today
DatabasesAuto-check passed
Paro Benchmark
zunor/paro
Run Paro engineering performance gates and exploratory cold/warm, cross-engine or operator comparisons.
105 GitHub stars~1.8k tokensUpdated today
DatabasesAuto-check passed

Works with

Questions about Lancedb Update Lance Dependency

What does Lancedb Update Lance Dependency do?

Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb. Lancedb Update Lance Dependency is an agent skill from lancedb/lancedb. Update LanceDB to a specific Lance release or tag.

When should I use Lancedb Update Lance Dependency?

Lancedb Update Lance Dependency fits situations like: bumping Lance dependencies in the lancedb repository; including Rust workspace Lance crates; java lance-core; branch creation.

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

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

How do I install Lancedb Update Lance Dependency in Codex?

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

Can I use Lancedb 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 lancedb/lancedb --skill lancedb-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/lancedb-update-lance-dependency, .gemini/skills/lancedb-update-lance-dependency, .github/skills/lancedb-update-lance-dependency and .opencode/skills/lancedb-update-lance-dependency in your project.

What does Lancedb Update Lance Dependency need to run?

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

Does Lancedb 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 Lancedb 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 Lancedb Update Lance Dependency use?

Lancedb 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 Lancedb Update Lance Dependency use?

About 1.1k tokens (SKILL.md is roughly 4.2k 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 Lancedb Update Lance Dependency?

Skills that share tags, products or a category with Lancedb Update Lance Dependency: Qdrant Clients SDK (qdrant/skills, 253 stars), Qdrant Advisor (qdrant/skills, 253 stars), Check Tools (oaustegard/claude-skills, 150 stars) and Qdrant Vector Search (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lancedb Update Lance Dependency?

lancedb (a GitHub organization) maintains it in lancedb/lancedb, which has 11,614 GitHub stars. The repository was last updated on October 7, 2026.

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

Install Lancedb 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

LanceDB Update Lance Dependency

Scope

Workflow

GitHub Actions

Files

Compare with similar skills

Similar skills

Qdrant Clients SDK

Qdrant Advisor

Check Tools

Qdrant Vector Search

Paro Optimizer

Paro Benchmark

Related

Questions about Lancedb Update Lance Dependency