gemini-commands

Create reusable Gemini CLI slash commands defined in TOML files.

21|Updated Jan 5, 2024
One-click install
npx skills add https://github.com/olafkfreund/nixos_config --skill gemini-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-commands
Source: https://github.com/olafkfreund/nixos_config/tree/main/.gemini/skills/gemini-commands
Command: npx skills add https://github.com/olafkfreund/nixos_config --skill gemini-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gemini users often need repeatable, task-specific prompts and workflows. This skill lets you define custom slash commands in TOML files and run them from the Gemini CLI, reducing manual prompt composition and context switching.

Core Features & Use Cases

  • Project-scoped commands: Place TOML command definitions under .gemini/commands to reuse across tasks and teammates.
  • Namespace and organization: Create namespaced commands like git/commit.toml for structured workflows.
  • Easy activation and runtime prompts: Commands load at invocation and support embedded prompts, shell execution, and file content injection.
  • Use Case: Define a /status command that summarizes repository changes, or a /deploy command sequence to run deployment steps.

Quick Start

Create a new command by adding a TOML file under .gemini/commands (or ~/.gemini/commands for user scope) with a short description and a prompt. Then invoke it via /<command-name> in Gemini.

Frequently Asked Questions about gemini-commands

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

FAQPage Schema
How do I create reusable Gemini CLI slash commands for local projects?

Create reusable Gemini CLI slash commands by defining prompts and metadata in TOML files placed under the .gemini/commands directory to automate development workflows. You then invoke these custom prompts directly from the Gemini CLI.

Can I use shell execution and file content injection in Gemini CLI workflows?

Gemini CLI workflows support shell execution and file content injection within custom slash commands defined in TOML files. This allows you to embed shell commands and file contents directly into your prompts for operational tasks.

What is the best way to organize task-specific prompts for development and testing teams?

Organize task-specific prompts by creating namespaced TOML files, such as git/commit.toml, under the project-scoped .gemini/commands directory. This structure enables teammates to share and reuse development and testing workflows consistently.

Does the Gemini CLI support user-scoped custom commands across different projects?

The Gemini CLI supports user-scoped custom commands by placing TOML command definitions in the ~/.gemini/commands directory. This makes your custom slash commands available across all local projects rather than just a single repository.

How do I automate deployment steps and repository summaries using Gemini?

Automate deployment steps and repository summaries by defining command sequences in TOML files with embedded prompts and shell execution. You can create a /deploy or /status command to run specific operational workflows on invocation.

Do I need TOML frontmatter to define custom Gemini commands?

TOML frontmatter is required to enforce metadata for custom Gemini commands, ensuring the structured, shell-aware prompt format loads correctly at invocation. This metadata defines the command description and scope.