Description
Many developers use multiple AI-powered CLI tools such as Claude Code and OpenCode. These tools follow the Agent Skills standard, but each stores skills in different default directories (e.g., ~/.claude/skills/ and ~/.config/opencode/skills/).
Currently, users of Gemini CLI must manually copy or link these expertise-rich directories to ~/.gemini/skills/ to leverage them.
I propose adding a new built-in command /sync-skills that:
- Automatically discovers skills from Claude Code and OpenCode directories.
- Safely creates symbolic links in the Gemini skills folder.
- Automatically avoids conflicts with built-in Gemini extensions.
- Cleans up broken or stale links.
Motivation
This feature will make Gemini CLI the central hub for AI engineering expertise by allowing users to instantly "import" their existing library of specialized skills from other tools without manual overhead or dependency conflicts.
Proposed Implementation
- Add a new command implementation in
src/commands/.
- Use a safe linking strategy that prioritizes official Gemini extensions.
- Provide clear feedback to the user on how many skills were synchronized.
Description
Many developers use multiple AI-powered CLI tools such as Claude Code and OpenCode. These tools follow the Agent Skills standard, but each stores skills in different default directories (e.g.,
~/.claude/skills/and~/.config/opencode/skills/).Currently, users of Gemini CLI must manually copy or link these expertise-rich directories to
~/.gemini/skills/to leverage them.I propose adding a new built-in command
/sync-skillsthat:Motivation
This feature will make Gemini CLI the central hub for AI engineering expertise by allowing users to instantly "import" their existing library of specialized skills from other tools without manual overhead or dependency conflicts.
Proposed Implementation
src/commands/.