DEV Community

Cover image for Skills across coding assistants
Nicolas Fränkel
Nicolas Fränkel

Posted on Originally published at blog.frankel.ch

Skills across coding assistants

I love Claude Code, but I use it so much that I regularly exhaust my weekly quota before the week ends. When that happens, I usually switch to other free-tier CLIs, e.g., Google Antigravity, GitHub Copilot, and, just last week, Mistral's Vibe. I really wanted to try Vibe to evaluate the feasibility of moving away from Claude Code in favor of a more sovereign solution.

Vibe only offers a single model by default, Mistral Medium 3.5. It hallucinated results badly, and I noticed it immediately. When I tried to understand what happened, I realized it hadn't triggered any of my lovingly crafted skills. The reason is that Claude Code stores skills in custom locations, in opposition to most other assistants.

I went through each assistant's documentation, so you don't get bitten the same way.

Assistant Personal Project
Claude Code ~/.claude/skills ./.claude/skills
Antigravity ~/.gemini/skills ./.agents/skills
Vibe
  • ~/.vibe/skills
  • ~/.agents/skills
  • ./.vibe/skills
  • ./.agents/skills
Copilot CLI
  • ~/.copilot/skills
  • ~/.agents/skills
  • ./.github/skills
  • ./.claude/skills
  • ./.agents/skills

The specification is pretty clear about it:

Scope Path Purpose
Project <project>/.<your-client>/skills/ Your client’s native location
Project <project>/.agents/skills/ Cross-client interoperability
User ~/.<your-client>/skills/ Your client’s native location
User ~/.agents/skills/ Cross-client interoperability

My conclusion is straightforward. Put skills in ~/.agents/skills and ./.agents/skills, then symlink ~/.claude/skills and ./.claude/skills to them. If the .claude/skills folders already exist, move their content to the .agents/skills ones first.

ln -s ~/.agents/skills ~/.claude/skills
ln -s ../.agents/skills .claude/skills        # 1
Enter fullscreen mode Exit fullscreen mode
  1. Run it from the project root

I love Claude Code, but it isn't a good citizen here. That's one more reason for me to try Vibe more seriously.

To go further:


Originally published at A Java Geek on November 8th, 2026.

Top comments (0)