Skills and MCP

Before running a project skill, the chat shows its path. A project skill replaces yours of the same name, and links leaving the project are ignored.

ai calls the CLIs themselves, so each one uses the skills and MCPs it already has. /sync gathers everything and installs in each tool what only exists in the others:

ai [auto] › /sync
Ferramentas encontradas: claude, codex, agy
  MCP   github                   codex → claude
  MCP   obsidian                 claude → codex
  skill humanizer                claude → codex  (~/.agents/skills/humanizer)
Aplicar? [s/N]

• MCPs are added through each CLI's own mcp add command, not by editing files by hand.
• The same server under different names is recognized by package or URL and not duplicated.
• MCPs that ship inside an app (like Codex.app's) stay there.
• Skills are shared by link: ~/.claude/skills, ~/.agents/skills (Codex) and ~/.gemini/antigravity/skills. Editing one applies to all three.
• Extra Claude accounts are refreshed too.
• MCP environment variables, which may hold tokens, are copied into the other tool's config. /sync warns before doing it.
• /sync --dry-run only shows what it would do.

Project skills and commands: the chat reads .claude/commands, .claude/skills, .agents/skills and .agent/workflows from the open project, plus the user folders. /pr-review 237 goes to Claude exactly as typed, and Claude runs the command natively. A skill that only exists in Codex or Antigravity goes to that tool, with the file's instructions in the request.

Since the chat doesn't forward approval prompts, an MCP tool only runs if it is already allowed in the CLI's permissions or the mode is auto or yolo. OpenRouter has no skills or MCP.