OpenSkillIndex← back to search
claude-codedevelopment

Claude-skill-registry gemini-command-development

Expert guide for creating custom Gemini CLI commands. Covers slash command definitions (.toml), argument parsing, and shell execution. Use when creating custom Gemini commands, defining TOML command files, adding command arguments, or building extension-based commands. Delegates to gemini-cli-docs.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/gemini-command-development" ~/.claude/skills/majiayu000-claude-skill-registry-gemini-command-development && rm -rf "$T"
manifest: skills/data/gemini-command-development/SKILL.md
tags
#gemini#cli#toml#command-line#automation#development
source content

Gemini Command Development

🚨 MANDATORY: Invoke gemini-cli-docs First

STOP - Before providing ANY response about Gemini Commands:

  1. INVOKE 
    gemini-cli-docs
    skill
  2. QUERY for the specific command topic
  3. BASE all responses EXCLUSIVELY on official documentation loaded

Overview

Expert skill for defining custom slash commands in the Gemini CLI. Unlike Claude Code's markdown-based commands, Gemini uses TOML configuration or Extension-based commands.

When to Use This Skill

Keywords: gemini commands, custom slash commands, .toml commands, command arguments, command alias

Use this skill when:

  • Creating custom commands in 
    commands.toml
    (or similar)
  • creating extension-based commands (
    <extension>/commands/*.toml
    )
  • Defining command arguments and defaults
  • Mapping commands to complex prompts

Command Structure (TOML)

Gemini commands are typically defined in TOML files within extensions or configuration.

[command-name]
description = "Description"
prompt = "The actual prompt to send..."

(Note: Verify exact syntax via 

gemini-cli-docs
as specific implementation details vary by version)

Keyword Registry (Delegates to gemini-cli-docs)

TopicQuery Keywords
Definition
custom commands toml
, 
define slash command
Arguments
command arguments
, 
command variables
Scope
workspace commands
, 
global commands

Quick Decision Tree

What do you want to do?

  1. Create a Simple Alias -> Query 
    gemini-cli-docs
    : "create custom command"
  2. Package Command in Extension -> Query 
    gemini-cli-docs
    : "extension commands structure"

Test Scenarios

Scenario 1: Create Custom Command

Query: "How do I create a custom slash command in Gemini CLI?" Expected Behavior:

  • Skill activates on "custom slash commands"
  • Delegates to gemini-cli-docs for TOML syntax Success Criteria: User receives TOML command definition example

Scenario 2: Extension Commands

Query: "How do I add commands to my Gemini extension?" Expected Behavior:

  • Skill activates on "extension commands"
  • Provides extension command structure Success Criteria: User receives extension commands path and format

Scenario 3: Command Arguments

Query: "How do I pass arguments to a Gemini command?" Expected Behavior:

  • Skill activates on "command arguments"
  • Delegates to docs for variable syntax Success Criteria: User receives argument handling pattern

References

Official Documentation: Query 

gemini-cli-docs
for:

  • "custom commands"
  • "slash commands"

Version History

  • v1.1.0 (2025-12-01): Added Test Scenarios section
  • v1.0.0 (2025-11-25): Initial release