Gemini CLI skills

Q: Where is the Gemini CLI skills folder?

`~/.gemini/skills/` for your user skills and `.gemini/skills/` in a project. The `.agents/skills/` alias works in both places.

Q: Can I use Claude Code skills in Gemini CLI?

The SKILL.md format is shared. Install the skill with `--agent gemini-cli` or copy the folder. Read it first: a skill can point to tools that Gemini CLI does not have.

Yes, Gemini CLI supports agent skills. A skill is a folder with a SKILL.md file. The file holds a name, a description and instructions. Gemini CLI reads the name and description of each skill at the start of a session. When your request matches a description, it asks for your consent to activate the skill, and loads the full instructions (Gemini CLI skills docs).

Skills use the same SKILL.md format as Claude Code, Codex and Cursor. A skill from GitHub can work in each of them.

Where Gemini CLI looks for skills

Gemini CLI finds skills in four tiers, lowest to highest precedence (docs):

Built-in skills that ship with Gemini CLI.
Extension skills bundled in extensions.
User skills in ~/.gemini/skills/ or ~/.agents/skills/.
Workspace skills in .gemini/skills/ or .agents/skills/ in your project.

The .agents/skills/ alias works with other agents that follow the Agent Skills standard. One folder can serve Gemini CLI and Codex in the same repo.

Workspace skills load when the folder is trusted. Run /trust in the session if a project skill does not show up (getting started tutorial).

How to install a skill

From a Git repo. Gemini CLI installs skills from a repo URL:

gemini skills install https://github.com/google-gemini/gemini-skills.git --path skills/gemini-api-dev

--path points to the skill folder inside the repo. --scope workspace installs to the project in place of your user folder. --consent skips the confirm prompt.

With the skills CLI. The open skills CLI has a gemini-cli agent flag. It installs to .agents/skills/ in the project, or to ~/.gemini/skills/ with -g:

npx skills add google-gemini/gemini-skills --skill gemini-api-dev --agent gemini-cli

By hand. Copy the skill folder into one of the folders above.

Commands to manage skills

In a session:

/skills list shows the skills Gemini CLI found.
/skills disable <name> and /skills enable <name> turn a skill off and on.
/skills reload picks up new or changed skills.

In the terminal:

gemini skills list --all lists every skill, built-in skills included.
gemini skills uninstall <name> --scope workspace removes a project skill.
gemini skills link . links a skill you are writing to your user folder for tests.

3 skills to try

1. gemini-api-dev (google-gemini/gemini-skills, Apache-2.0) For code that calls the Gemini API: text, chat, images, speech, function calling and structured output.

2. review-duplication (google-gemini/gemini-cli, Apache-2.0) The Gemini CLI repo keeps this skill in its own .gemini/skills/ folder. During a code review it looks for duplicated code and shared utilities you could reuse. It is a good model of a team skill.

npx skills add google-gemini/gemini-cli --skill review-duplication --agent gemini-cli

3. python-anti-patterns (wshobson/agents, MIT) A checklist of bad Python practices for reviews. It is not Gemini-specific. It shows that a skill written for other agents can install into Gemini CLI.

npx skills add wshobson/agents --skill python-anti-patterns --agent gemini-cli

Read each SKILL.md before you install. A skill can tell the agent to run scripts.

How to write a Gemini CLI skill

Ask Gemini CLI to make one. The built-in skill-creator skill builds the folder, the SKILL.md and the scripts/, references/ and assets/ folders (docs).

To write one by hand, follow the rules in the tutorial:

The file name must be SKILL.md, at the root of the skill folder or one level down.
The front matter comes first and holds name and description.
The skill name comes from name:, not from the folder name.
The description decides when Gemini CLI uses the skill. Name the tasks and the words that should trigger it.

Our SKILL.md format guide covers the fields in more depth.

Skills vs GEMINI.md

GEMINI.md holds context that applies to every session in a project. A skill loads on demand, when a task matches. Put your project facts in GEMINI.md. Put a procedure you run for some tasks in a skill.

Find skills for your repo

Our database lists open-license skills from GitHub with an install command for each. The free scan reads your repo URL or a description and shows how many skills match, plus 2 picks. The full curated list costs $9, paid one time: up to 30 picks ranked, with install commands and a reason for each (pricing).

FAQ

Does Gemini CLI support agent skills? Yes. It reads SKILL.md files from built-in, extension, user and workspace folders.

Where is the Gemini CLI skills folder? ~/.gemini/skills/ for your user skills and .gemini/skills/ in a project. The .agents/skills/ alias works in both places.

Can I use Claude Code skills in Gemini CLI? The SKILL.md format is shared. Install the skill with --agent gemini-cli or copy the folder. Read it first: a skill can point to tools that Gemini CLI does not have.

Does Gemini CLI have a skills marketplace? Skills install from Git repos and from extensions. Our database lists open-license skills from many repos, with an install command for each.

Checked 2026-10-23. Prices and policies change. Confirm on the source before you buy.

Gemini CLI skills

Where Gemini CLI looks for skills

How to install a skill

Commands to manage skills

3 skills to try

How to write a Gemini CLI skill

Skills vs GEMINI.md

Find skills for your repo

FAQ

Sources

More guides