How to Install i-have-adhd for Gemini CLI: Command vs Extension Setup

You can install i-have-adhd for Gemini CLI either as an opt-in custom command by placing gemini.toml in ~/.gemini/commands, or as an always-on extension via gemini extensions install https://github.com/ayghri/i-have-adhd, both leveraging the core ADHD-friendly rules defined in skills/i-have-adhd/SKILL.md and GEMINI.md.

The ayghri/i-have-adhd repository provides a specialized skill that reformats Gemini CLI responses to prioritize clarity, action items, and structured bullet points—ideal for users who prefer concise, high-density information. Installing this tool allows you to receive responses that follow specific ADHD-friendly conventions, whether you need occasional assistance or want every conversation structured this way.

Choose Your Installation Method

Gemini CLI supports two distinct ways to load the i-have-adhd skill, each suited to different workflows.

Custom Command (Opt-In): Place the gemini.toml file from skills/i-have-adhd/agents/ into ~/.gemini/commands. This creates a slash command (/i-have-adhd) that activates the skill rules only when explicitly invoked during a session.

Extension (Always-On): Install the repository as a CLI extension. This loads GEMINI.md and gemini-extension.json automatically, applying the ADHD-friendly formatting from the first message of every conversation without manual activation.

Method 1: Install as a Custom Command

This lightweight approach stores the skill as a command file that you trigger manually. The configuration resides in skills/i-have-adhd/agents/gemini.toml within the repository.

Create the commands directory and download the configuration file:

mkdir -p ~/.gemini/commands
curl -fsSL https://raw.githubusercontent.com/ayghri/i-have-adhd/main/skills/i-have-adhd/agents/gemini.toml \
     -o ~/.gemini/commands/i-have-adhd.toml

This places the TOML file at ~/.gemini/commands/i-have-adhd.toml, containing the prompt template that enforces the ADHD-friendly response rules.

Activate the Skill in a Session

Start a new Gemini CLI session and type:

/i-have-adhd

The skill becomes active immediately for that session only, modifying subsequent responses according to the rules in SKILL.md.

Method 2: Install as an Always-On Extension

For persistent application across all conversations, install the repository as a Gemini CLI extension:

gemini extensions install https://github.com/ayghri/i-have-adhd

This command clones the repository and reads gemini-extension.json, which instructs Gemini CLI to load GEMINI.md. The markdown file imports the full rule set from skills/i-have-adhd/SKILL.md, ensuring every response follows ADHD-friendly formatting without requiring the slash command.

Verify the Installation

Confirm successful setup using repository-specific commands.

For the custom command route:

ls ~/.gemini/commands

You should see i-have-adhd.toml listed. You can also type / in a running Gemini session and verify that i-have-adhd appears in the autocomplete list.

For the extension route:

gemini extensions list

The output should display i-have-adhd among installed extensions.

Update or Remove the Skill

Maintenance commands differ based on your installation method.

Updating:

For the custom command, rerun the original curl command to overwrite the file:

curl -fsSL https://raw.githubusercontent.com/ayghri/i-have-adhd/main/skills/i-have-adhd/agents/gemini.toml \
     -o ~/.gemini/commands/i-have-adhd.toml

For the extension, use the CLI's built-in update mechanism:

gemini extensions update i-have-adhd

Uninstalling:

Remove the custom command file:

rm ~/.gemini/commands/i-have-adhd.toml

Or uninstall the extension:

gemini extensions uninstall i-have-adhd

Summary

• Two installation paths exist: An opt-in custom command (~/.gemini/commands/i-have-adhd.toml) for manual activation, or an always-on extension via gemini extensions install.
• Core rules reside in skills/i-have-adhd/SKILL.md and GEMINI.md, with the command route using skills/i-have-adhd/agents/gemini.toml as the entry point.
• Activation differs by method: The custom command requires typing /i-have-adhd per session, while the extension applies rules automatically via gemini-extension.json.
• Updates are route-specific: Use curl for commands and gemini extensions update for extensions.

Frequently Asked Questions

What is the difference between the custom command and extension installation methods?

The custom command method places gemini.toml in ~/.gemini/commands, creating an opt-in /i-have-adhd slash command that activates the skill only when you type it during a session. The extension method installs the full repository as a plugin that loads GEMINI.md automatically, making the ADHD-friendly rules active from the first message of every conversation without manual invocation.

Where are the core ADHD-friendly response rules defined in the repository?

The source of truth for the ten ADHD-friendly response rules is skills/i-have-adhd/SKILL.md. The custom command in skills/i-have-adhd/agents/gemini.toml references these rules in its prompt template, while the extension route loads them through GEMINI.md, which imports the skill definitions for always-on application.

Can I use both the custom command and extension methods simultaneously?

Yes, you can install both methods simultaneously. However, if you have the extension active, the rules are already applied to every message, making the custom command redundant unless you want to explicitly re-invoke or verify the formatting rules at a specific point in the conversation.

How do I update the i-have-adhd skill to the latest version from the main branch?

For custom command installations, rerun the curl command to download the latest gemini.toml from the main branch to ~/.gemini/commands/i-have-adhd.toml. For extension installations, execute gemini extensions update i-have-adhd to fetch the latest repository changes and reload GEMINI.md and gemini-extension.json.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}