Skip to content

Port a skill to another agent

Last reviewed October 24, 2026

Before you port anything, search this site (search). The skill you are about to rewrite may already exist for your agent. If it exists for a different one, porting is usually a few minutes' work, because most of a skill was never specific to an agent in the first place.

What carries over

A skill that uses only the standard's six frontmatter fields (name, description, license, compatibility, metadata, allowed-tools) and plain instructions works in every agent that follows the standard: Claude Code, Codex, Gemini CLI, Copilot, Cursor, OpenCode and Antigravity. For those, porting means putting the folder where the other agent looks.

What differs

  • The folder. Claude Code reads .claude/skills/; most of the others read .agents/skills/, and Copilot, Cursor and OpenCode read both (the table is on the write step).
  • Extra frontmatter. Fields like when_to_use, argument-hint and disable-model-invocation are Claude Code's own (Claude Code skills). Fold what they say into the description, or move them out. Codex reads optional settings from its own agents/openai.yaml file beside SKILL.md.
  • Which copy wins. If the same skill is installed personally and in a project, Claude Code uses the personal one; the standard's convention, and Gemini CLI, use the project's. Keep one copy, or expect the two to behave differently.
  • How it is called by name. Claude Code and Cursor use /writing-release-notes; Codex uses $writing-release-notes (Codex skills). Gemini CLI asks the user before it activates a skill.
  • Tool names in the instructions. "Use the Bash tool" or "call WebFetch" names a Claude Code tool another agent may not have. Write the action instead ("run", "fetch the page") and let each agent use what it has.
  • allowed-tools. The standard calls it experimental and agents treat it differently, so a skill should not depend on it to work.

Install once for several agents

The skills command from Vercel installs a skill for the agents you name, and handles the folder problem by keeping one copy and linking the others to it (vercel-labs/skills). For Claude Code and Codex in one project:

shell
npx skills add your-name/your-skills -a claude-code -a codex
what it creates
.agents/skills/writing-release-notes/SKILL.md
.claude/skills/writing-release-notes -> ../../.agents/skills/writing-release-notes

One file to edit, two agents reading it.

port-skill does the rewriting

For anything beyond moving a folder, such as a Claude Code plugin, a slash command, or a skill full of one agent's tool names, port-skill is a skill that ports skills, plugins and slash commands between Claude Code, Codex, Antigravity and Gemini CLI.

  1. Install port-skill in the agent where the original works.
  2. Point it at the skill's folder or repository and name the agent you want it for.
  3. Read what it writes. Tool names, frontmatter and permission models differ enough that a quick review catches what did not translate.
  4. Once it works, submit the ported version here (submit a listing), so the next person searching for it on that agent finds it.

Building something else? See the guides to a plugin or marketplace and an MCP server.