gemini-command-development

Create custom Gemini CLI slash commands using TOML configuration files.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/DTMC-marketplace/governance --skill gemini-command-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-command-development
Source: https://github.com/DTMC-marketplace/governance/tree/main/skills/gemini-command-development
Command: npx skills add https://github.com/DTMC-marketplace/governance --skill gemini-command-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the creation of custom command-line interface commands for the Gemini CLI, enabling users to extend its functionality with their own tailored commands.

Core Features & Use Cases

  • TOML Command Definition: Guides users on defining commands using TOML configuration files.
  • Argument Parsing: Explains how to define and handle arguments for custom commands.
  • Extension-Based Commands: Details how to integrate commands within Gemini extensions.
  • Use Case: A developer wants to create a new Gemini command that summarizes code files. This Skill will guide them through defining the command, its arguments (like file path), and how to link it to a specific prompt.

Quick Start

Use the gemini-command-development skill to learn how to define a new custom slash command in Gemini CLI using TOML.

Frequently Asked Questions about gemini-command-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom commands for the Gemini CLI?

To create custom commands for the Gemini CLI, you define command syntax and arguments using TOML configuration files and map them to specific prompts within an extension-based structure.

What are extension-based commands in the Gemini CLI?

Extension-based commands in the Gemini CLI are custom slash commands integrated within Gemini extensions, allowing you to extend CLI functionality by mapping defined TOML configurations to actionable prompts.

How do I define command arguments using TOML for my CLI tool?

You define command arguments using TOML by specifying the argument syntax within a configuration file, which the Gemini CLI then parses to handle inputs like file paths for your custom commands.

Do I need to understand TOML to build Gemini CLI extensions?

Yes, understanding TOML is required to build Gemini CLI extensions, as this Skill relies on TOML configuration files to define command syntax, arguments, and map commands to prompts.

What is the best way to map a custom command to a prompt in Gemini extensions?

The best way to map a custom command to a prompt in Gemini extensions is by configuring the prompt linkage directly within your TOML command definition, tying the parsed arguments to the desired output generation.