Published: May 11, 2026
Category: Tutorials
Google's Gemini CLI supports the SKILL.md standard, meaning the same skills that work in Claude Code and Codex CLI work here without modification. Here's how to set them up.
> Quick Answer: Gemini CLI stores personal skills in ~/.gemini/skills/ and project-specific skills in .gemini/skills/ within the project root. Skills are directory-based, each containing a SKILL.md file, which is compatible across Claude Code and Codex CLI.
Personal skills: ~/.gemini/skills/
Project skills: .gemini/skills/ in your project root.
The directory structure is identical to Claude Code — each skill is a folder containing a SKILL.md file:
~/.gemini/skills/
├── code-reviewer/
│ └── SKILL.md
└── test-generator/
└── SKILL.md
# Create the skills directory
mkdir -p ~/.gemini/skills/
Download a skill from Agensi
unzip code-reviewer.zip -d ~/.gemini/skills/
Verify
ls ~/.gemini/skills/code-reviewer/SKILL.md
Start a new Gemini CLI session. The skill is active.
Because Claude Code, Codex CLI, and Gemini CLI all use SKILL.md, you can share skills across all three with symlinks:
# Use Claude Code skills as the source of truth
ln -s ~/.claude/skills/ ~/.gemini/skills
ln -s ~/.claude/skills/ ~/.codex/skills
One set of skills, every agent. This is the core value of the SKILL.md open standard — no vendor lock-in.
The SKILL.md format is identical. The only differences:
~/.gemini/skills/ instead of ~/.claude/skills/Every skill on Agensi works with Gemini CLI. The marketplace marks skills with their compatible agents. Filter by "Universal" to see skills tested across multiple agents.
Browse Gemini CLI compatible skills at Agensi.