gemini-extension-development

To create a Gemini CLI extension, you define custom slash commands using `.toml` files and configure the extension manifest. This Skill guides you through structuring the extension anatomy and defining command syntax for local development and testing.

The GEMINI.md context file provides essential context and instructions to the Gemini CLI when building extensions. It defines behavior and parameters, ensuring the extension operates correctly within the Gemini CLI environment.

You can link a local Gemini extension for hot-reloading by using local development workflows. This allows you to test extension commands and MCP integration locally before proceeding to publish or package the extension.

Integrating an MCP server into a Gemini CLI extension involves packaging the server and configuring it within the extension manifest. This provides extended capabilities and tool integration for the Gemini CLI environment during development.

The publishing workflow for a Gemini CLI extension involves packaging MCP servers, finalizing the extension manifest, and executing release processes. This supports installation from various sources to distribute your custom Gemini extensions.

Yes, understanding extension manifest files is required to build Gemini CLI extensions. You must define command syntax, configure GEMINI.md context, and manage the release processes to successfully create and publish extensions.