Setup Dev
relytcloud/pg_ducklake
Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.
A skill your agent uses when designing, implementing, reviewing, or debugging onetcli IPC database drivers, driver.json manifests, extension-protocol wire methods, schema metadata, DDL builders…
Install Ipc Driver Development
$ npx skills add feigeCode/navop --skill ipc-driver-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install feigeCode/navop ipc-driver-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/ipc-driver-development .claude/skills/ipc-driver-development && rm -rf skills-srcUse ~/.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/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .claude/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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 install https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-developmentType 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.
$ npx skills add feigeCode/navop --skill ipc-driver-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install feigeCode/navop ipc-driver-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/ipc-driver-development .agents/skills/ipc-driver-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .agents/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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.
$ npx skills add feigeCode/navop --skill ipc-driver-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install feigeCode/navop ipc-driver-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/ipc-driver-development .cursor/skills/ipc-driver-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .cursor/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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 https://github.com/feigeCode/navop.git --path .codex/skills/ipc-driver-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add feigeCode/navop --skill ipc-driver-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install feigeCode/navop ipc-driver-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/ipc-driver-development .gemini/skills/ipc-driver-development && rm -rf skills-srcUse ~/.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/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .gemini/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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.
$ gh skill install feigeCode/navop ipc-driver-developmentInstalls 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).
$ npx skills add feigeCode/navop --skill ipc-driver-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/ipc-driver-development .github/skills/ipc-driver-development && rm -rf skills-srcUse ~/.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/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .github/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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.
$ npx skills add feigeCode/navop --skill ipc-driver-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install feigeCode/navop ipc-driver-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/feigeCode/navop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/ipc-driver-development .opencode/skills/ipc-driver-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ipc-driver-development" agent skill from https://github.com/feigeCode/navop/tree/main/.codex/skills/ipc-driver-development into .opencode/skills/ipc-driver-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipc-driver-development", 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
ipc-driver-development- GitHub stars
- 1.8k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,193 words
- Files
- 6 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when designing, implementing, reviewing, or debugging onetcli IPC database drivers, driver.json manifests, extension-protocol wire methods, schema metadata, DDL builders…
- Works in 9 steps: Inspect the existing driver and host… → Design or update driver.json first.… → Split routing into control-plane and… → …
- Debugging onetcli IPC database drivers
- SKILL.md covers Overview, Workflow, Reference Routing and Required Guardrails, plus 2 more sections
- Calls cargo, bash and node
What it does
Ipc Driver Development is an agent skill from feigeCode/navop. Use when designing, implementing, reviewing, or debugging onetcli IPC database drivers, driver.json manifests, extension-protocol wire methods, schema metadata, DDL builders, import/export, packaging, or cross-language driver runtimes.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/language-patterns.md` and `references/manifest.md`).
It sits in Development. It works with DuckDB. The repository describes itself as: A native, all-in-one workspace for databases, SSH, SFTP, terminals, remote desktop, monitoring, and AI.
When your agent uses it
- Debugging onetcli IPC database drivers
- Driver.json manifests
- Extension-protocol wire methods
- Schema metadata
Example prompts
- “/ipc-driver-development”
Requirements
- Node.js
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Inspect the existing driver and host contract before editing. In this repo, use extensions/ipc/duckdb as the concrete reference; in the…
- Design or update driver.json first. Declare only methods that the binary actually handles, set dialect/capabilities so the host knows…
- Split routing into control-plane and connection-scoped methods. Keep init, conn/test, conn/open, and pure DDL builders independent of a…
- Implement metadata from database catalog truth, not UI labels, connection names, or hardcoded defaults. If the database has a current…
- Prefer explicit NotSupported / method-not-found behavior for missing methods. This lets the host use fallback behavior such as…
- For special connection lifecycle needs, declare them in driver.json.connection before changing host manager logic. The host should consume…
- For UI grouping such as domestic databases, declare top-level manifest metadata such as "category": "domestic_database". Do not make the…
- Add protocol-level tests before broad packaging work. Verify request JSON, response JSON, error codes, cancellation, fallback behavior…
- Build and package with the repository scripts, then verify the archive contains driver.json, binary, locales, and expected entry command.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cf8b2a. 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:
cargobashnoderustc
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ipc Driver Development loads about 2.4k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 1,193 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,193 words (~2,445 tokens).
“Build onetcli IPC database drivers from the host contract outward: driver.json declares the surface, extension-protocol defines wire JSON, and the driver routes each declared method to real database behavior.”
- name
- ipc-driver-development
Files
SKILL.md and 5 other files (references) in .codex/skills/ipc-driver-development of feigeCode/navop.
- SKILL.md
- agents/openai.yaml
- references/language-patterns.md
- references/manifest.md
- references/protocol.md
- references/testing-packaging.md
Open the folder on GitHubat commit 1cf8b2a
Compare with similar skills
Ipc Driver Development 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ipc Driver Development this skillfeigeCode/navop | 1.8k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Setup Devrelytcloud/pg_ducklake | 143 | — | ~2k | Automated safety check: Notes | MIT | |
| Lance Duckdb Update Lance Dependencylance-format/lance-duckdb | 129 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Tracelab Public Releaseuw-syfi/TraceLab | 138 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| DB AI GitHub Paper Weekly Newsdigoal/blog | 8.6k | — | ~1.2k | Automated safety check: Pass | GPL-2.0 | |
| DB AI GitHub Paper Weekly Newsdigoal/blog | 8.6k | — | ~2.4k | Automated safety check: Pass | GPL-2.0 |
Similar skills
Lance Duckdb Update Lance Dependency
lance-format/lance-duckdb
Update lance-duckdb to a specific Lance release or tag. An agent skill from lance-format/lance-duckdb.
Tracelab Public Release
uw-syfi/TraceLab
Publish TraceLab snapshots from the internal repo to the public uw-syfi/TraceLab GitHub repo as clean, mergeable, incremental pull requests from a persistent public mirror branch.
DB AI GitHub Paper Weekly News
digoal/blog
抓取并汇总"数据库、AI、GitHub、AI 论文"近 1 周新闻，输出图文并茂（含 mermaid 图）的 markdown 周报到当前项目的 markdown/ 目录。覆盖 10 个数据源：postgresweekly.com/issues（自动解析最新 issue…
DB AI GitHub Paper Weekly News
digoal/blog
抓取并分析"数据库、AI、GitHub、AI论文"相关的近1周内最新内容，分类汇总，输出图文并茂（含内置 Mermaid 图）的 Markdown 周报到当前项目的 markdown/ 目录。
Cognee Community Packages
topoteretes/cognee
Guide to using and contributing cognee community packages: database adapters, data-source connectors, custom tasks and retrievers, and Keywords AI observability.
More from feigeCode/navop
All 8 skills in this repoConnection Import Wasm
feigeCode/navop
A skill your agent uses when implementing, debugging, packaging, or host-enabling onetcli WASM connection importers such as DBeaver, Navicat, Navicat Lite, Termius, connection-import.wit components…
Gpui Component
feigeCode/navop
How to use the gpui-component UI library in GPUI applications, and the normative Design and Coding Guides that govern it.
Navop Release Notes
feigeCode/navop
A skill your agent uses when working in the Navop repository on CHANGELOG.md, version-tag preparation, GitHub Releases, or R2 updater release notes, especially when bilingual Chinese and English…
Ssh Connection Import
feigeCode/navop
A skill your agent uses when implementing or debugging onetcli SSH connection importers, including OpenSSH config, knownhosts, candidate file manifests, local composite installs, SSH authmethod JSON…
Gpui
feigeCode/navop
GPUI framework knowledge covering actions/keybindings, async/background tasks, context management (App/Window/Context<T/AsyncApp), custom elements (low-level Element trait), entity state management…
Navop
feigeCode/navop
Use terminal commands to discover and operate resources exposed by a running Navop desktop application through its host-authoritative Public MCP runtime.
Related
Works with
Categories
Questions about Ipc Driver Development
What does Ipc Driver Development do?
A skill your agent uses when designing, implementing, reviewing, or debugging onetcli IPC database drivers, driver.json manifests, extension-protocol wire methods, schema metadata, DDL builders…. Ipc Driver Development is an agent skill from feigeCode/navop.json manifests, extension-protocol wire methods, schema metadata, DDL builders, import/export, packaging, or cross-language driver runtimes.
When should I use Ipc Driver Development?
Ipc Driver Development fits situations like: debugging onetcli IPC database drivers; driver.json manifests; extension-protocol wire methods; schema metadata.
How do I install Ipc Driver Development in Claude Code?
Run `npx skills add feigeCode/navop --skill ipc-driver-development -a claude-code`. Or copy the skill folder (.codex/skills/ipc-driver-development in feigeCode/navop) into .claude/skills/ipc-driver-development in your project. Claude Code loads it when a task matches its description.
How do I install Ipc Driver Development in Codex?
Run `npx skills add feigeCode/navop --skill ipc-driver-development -a codex`. Or copy the skill folder (.codex/skills/ipc-driver-development in feigeCode/navop) into .agents/skills/ipc-driver-development in your project. Codex loads it when a task matches its description.
Can I use Ipc Driver Development 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 feigeCode/navop --skill ipc-driver-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ipc-driver-development, .gemini/skills/ipc-driver-development, .github/skills/ipc-driver-development and .opencode/skills/ipc-driver-development in your project.
What does Ipc Driver Development need to run?
Going by SKILL.md and its folder, Ipc Driver Development needs the command-line tools its instructions call (cargo, bash, node and rustc). Our summary lists: Node.js.
Does Ipc Driver Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ipc Driver Development 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 Ipc Driver Development use?
Ipc Driver Development has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Ipc Driver Development use?
About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.9k tokens, read only when the agent opens those files.
What are the alternatives to Ipc Driver Development?
Skills that share tags, products or a category with Ipc Driver Development: Setup Dev (relytcloud/pg_ducklake, 143 stars), Lance Duckdb Update Lance Dependency (lance-format/lance-duckdb, 129 stars), Tracelab Public Release (uw-syfi/TraceLab, 138 stars) and DB AI GitHub Paper Weekly News (digoal/blog, 8.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipc Driver Development?
feigeCode (a GitHub user) maintains it in feigeCode/navop, which has 1,806 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: feigeCode/navop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.