Repository navigation
Sharing with pi and Claude Code
Dive, pi and Claude Code read the same skill format, so one copy of a skill can serve all three. This page sets up a single shared copy, explains how to handle a repository that also contains a pi extension, and shows what can and can't be shared between the apps.
| App | Reads skills from |
|---|---|
| Dive |
~/dive/skills, ~/.agents/skills, and the extra folders you add in Settings > SKILLS |
| pi |
~/.pi/agent/skills, ~/.agents/skills, pi packages, and the skills list in pi's settings |
| Claude Code | ~/.claude/skills |
~/.agents/skills is the folder Dive and pi both read. Claude Code can reach it through a symbolic link.
-
Keep each shared skill in
~/.agents/skills. If the skill lives in a git repository, clone it there, so that updating it is agit pull:git clone https://github.com/<you>/<skill-repo>.git ~/.agents/skills/<skill-repo>
Dive and pi look for
SKILL.mdinside subfolders too, so a repository that keeps its skill inskills/<name>/works as it is. -
Link the skill into Claude Code's folder. Link the folder that contains
SKILL.md:mkdir -p ~/.claude/skills ln -s ~/.agents/skills/<skill-repo> ~/.claude/skills/<name>
If the repository keeps the skill in
skills/<name>/, link that inner folder instead:ln -s ~/.agents/skills/<skill-repo>/skills/<name> ~/.claude/skills/<name>
Dive follows symbolic links too, so links work in its folders as well.
-
Don't copy the skill anywhere else. With two copies, each app keeps whichever it finds first, and the other one goes out of date without anyone noticing.
Some repositories hold a skill and a pi extension together, for example a skill plus a picker or a command for pi. Load the extension from the same clone, by listing the clone as a local path in ~/.pi/agent/settings.json:
{
"packages": ["/absolute/path/to/.agents/skills/<skill-repo>"]
}pi uses a local path where it is, without copying it. Two things bring the duplicate back:
-
A
git:entry for the same repository, for example frompi install git:github.com/<you>/<skill-repo>. pi clones the whole repository, skill included, into~/.pi/agent/git/, and installs it again when that folder is missing, so deleting the clone doesn't help. Remove thegit:entry instead. -
A
"skills": []filter on the local entry, when the repository'spackage.jsonlists the skill underpi.skills. The filter then hides the skill from pi completely, including the copy pi would find through~/.agents/skills.
-
Edit and test the skill in your own working copy, then commit and push.
-
Pull the change into the shared clone:
git -C ~/.agents/skills/<skill-repo> pull
-
In pi, run
/reloador start a new session. Dive picks the change up within two seconds. Claude Code reads the linked folder, so it sees the same files.
Don't edit files inside the shared clone directly: your next git pull could clash with those edits. For a local path, pi update has nothing to download; the pull is the update.
- Dive keeps the first one it finds, looking in
~/dive/skills, then~/.agents/skills, then your extra folders, and lists the other as not loaded. - pi warns about the clash and keeps the first skill it found.
Give every skill a unique name, and keep one copy of each.
| Dive | pi | Claude Code | |
|---|---|---|---|
Skills (SKILL.md) |
Yes | Yes | Yes |
| MCP servers | Yes, in llama.cpp, LM Studio and Ollama mode | No | Yes |
| Dive's external and custom tools | Yes | No | No |
| pi extensions | Only in Pi mode, where pi runs them | Yes | No |
To give all three apps the same tool, the closest you can get is an MCP server for Dive and Claude Code, and a pi extension for pi.
You can add ~/.claude/skills as an extra folder in Dive's Settings > SKILLS, and pi's settings can list it under skills. That works, but it makes each app depend on a folder another app owns. A neutral ~/.agents/skills that belongs to none of them avoids that.
These pages describe Dive 5.0.8. Source code: DuckTapeKiller/dive. Spotted a mistake? Open an issue.
Get started
Tools and skills
Build your own
Share and stay safe
How Dive works
Help