claude-to-gemini-converter

name	claude-to-gemini-converter
description	Converts a Claude agent configuration (often from platforms like Nexus) into a valid Gemini CLI agent markdown file. Use this when a user asks to migrate or convert a Claude agent to Gemini.
tools	["run_shell_command","read_file","write_file","replace","grep_search","glob"]

Claude to Gemini Agent Converter Skill

This skill provides the procedural workflow and specialized mapping instructions necessary to accurately convert a Claude agent definition into a valid Gemini CLI agent.

How to Convert an Agent

When asked to convert a Claude agent, follow this step-by-step procedure:

1. Extract and Convert the Name: Extract the agent's name. Convert it to a valid Gemini CLI slug format (lowercase, digits, and hyphens only: ^[a-z0-9-_]+$). Example: "Social Media Strategist" -> social-media-strategist

2. Map the Tools: Read the Claude agent's list of tools and translate them to the exact Gemini CLI equivalents. CRITICAL: Review the specific tool mappings and handling strategies detailed in: references/tool-mapping.md

3. Filter Frontmatter: Remove unsupported fields from the Claude frontmatter (e.g., color). Ensure you include standard Gemini local agent fields:

   • kind: local
   • name: <slug>
   • description: <extracted description>
   • tools: [...] (the converted array of tools)

4. Preserve the System Prompt: The entire body of the Claude agent (its persona, rules, examples) becomes the body of the Gemini CLI markdown file (everything below the YAML --- frontmatter block).

5. Inject Operational Guidelines: If the Claude agent utilized any tools that do not have direct 1:1 Gemini CLI equivalents (such as TaskOutput, KillShell, LSP, TaskCreate, or calling sub-Agents), you MUST append the special instruction boilerplate to the very end of the markdown body. See the boilerplate in: references/tool-mapping.md

6. Create the File: Save the final converted markdown to the project's local agent directory: .gemini/agents/<slug>.md.

Example Execution

If the user provides:

---
name: QA Tester
tools: WebFetch, Bash, TaskOutput
---
# QA Tester Agent
You are an expert QA tester...

You should output to .gemini/agents/qa-tester.md:

---
kind: local
name: qa-tester
description: QA Tester agent
tools:
  - web_fetch
  - run_shell_command
---
# QA Tester Agent
You are an expert QA tester...

## Operational Guidelines & Tool Usage
To accomplish your tasks, you must adapt to the following tool usage patterns:
- **Background Tasks & Output**: To run a long-running task, use `run_shell_command` with `is_background: true`. Redirect the output to a file (e.g., `command > output.log &`). To check the task's output, use `run_shell_command` to `cat output.log` or use `read_file`.