Skip to main content
All docs

Gemini CLI

Install Edaskills skills into Gemini CLI — skill directory plus a GEMINI.md pointer and MCP bridge.

Gemini CLI

Gemini CLI reads project instructions from GEMINI.md. It does not read a SKILL.md directory natively, so the Edaskills CLI lands the skill files and appends a pointer line to GEMINI.md.

Install with the CLI

edaskills install <slug> --agent gemini_cli

This does two things:

  1. Lands the skill at ~/.edaskills/skills/<slug>/ (flattened, with references and scripts).
  2. Appends a pointer line to <repo>/GEMINI.md: when a task matches <slug>, read <path>/SKILL.md and follow its instructions. If the same line already exists it is skipped, so re-installing does not duplicate it.

The append shows a diff and asks for confirmation first; pass --yes to skip the prompt in CI. Existing GEMINI.md content is never overwritten. If the skill directory already exists the CLI stops and suggests edaskills update, which backs up the old directory before writing.

MCP config

For MCP, bridge the remote endpoint through mcp-remote (stdio). Create an API key under Settings → API keys, export it as EDASKILLS_API_KEY, and configure your host to run:

npx -y mcp-remote https://edaskills.com/api/v1/mcp \
  --header "Authorization: Bearer ${EDASKILLS_API_KEY}"

The --header value contains a space, so quote it as a whole. ${EDASKILLS_API_KEY} is expanded from the environment — never commit a plaintext key. MCP lets the agent discover skills, read content and request an install plan; it does not write to disk.

Verification status

The GEMINI.md pointer convention above is what the Edaskills CLI does today. A "verified on Gemini CLI" badge would require an actual demo run executed on this host; none is recorded yet, so no host badge is shown.

See also: Install a skill.