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 |
|
|
Antigravity |
|
|
Vibe |
|
|
Copilot CLI |
|
|
The specification is pretty clear about it:
| Scope | Path | Purpose |
|---|---|---|
Project |
|
Your client’s native location |
Project |
|
Cross-client interoperability |
User |
|
Your client’s native location |
User |
|
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)
| 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.