Repository navigation
New post: Skills across coding assistants #435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,61 @@ | ||
| --- | ||
| title: "Skills across coding assistants" | ||
| date: "2026-11-13" | ||
| description: "Claude Code reads skills from its own folders, while other assistants also scan .agents/skills. Where each one looks, and how symlinks fix it." | ||
| canonical: "https://blog.frankel.ch/skills-across-coding-assistants/" | ||
| authors: | ||
| - "nicolas-frankel" | ||
| image: "cover_large.jpg" | ||
| categories: | ||
| - "AI" | ||
| - "Tools" | ||
| related_posts: | ||
| - "writing-an-agent-skill" | ||
| - "how-to-create-test-install-agent-skills" | ||
| - "best-practices-for-working-with-ai-agents-subagents-skills-and-mcp" | ||
| - "context-is-a-budget-ai-coding-agents-team-process" | ||
| --- | ||
|
|
||
| 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](https://agentskills.io/client-implementation/adding-skills-support#where-to-scan) is pretty clear about it: | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Distinguish the scan recommendation from the specification. The linked guidance recommends these paths for interoperability, but explicitly says the specification does not mandate skill directory locations. Present the table as guidance rather than a specification requirement. (agentskills.io)
|
||
|
|
||
| | 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Include Antigravity in the personal-skill setup. The recommended setup places personal skills in
|
||
|
|
||
| ```bash | ||
| ln -s ~/.agents/skills ~/.claude/skills | ||
| ln -s ../.agents/skills .claude/skills # 1 | ||
|
Comment on lines
+44
to
+45
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove the old directories before creating the links. Moving the contents leaves each
|
||
| ``` | ||
|
|
||
| 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:** | ||
|
|
||
| * [Agent skills specification: where to scan](https://agentskills.io/client-implementation/adding-skills-support#where-to-scan) | ||
| * [Google: Antigravity App skill locations](https://antigravity.google/docs/skills#antigravity-app-skill-locations) | ||
| * [Vibe: skill locations](https://docs.mistral.ai/vibe/code/cli/skills#locations) | ||
| * [Copilot: finding and storing skills](https://docs.github.com/en/copilot/concepts/customizations/agent-skills#finding-and-storing-skills) | ||
|
|
||
| <hr> | ||
|
|
||
| _Originally published at [A Java Geek](https://blog.frankel.ch/skills-across-coding-assistants/) on November 8<sup>th</sup>, 2026._ | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
sed -n '1,61p' content/posts/2026/11/13/skills-across-coding-assistants/index.mdRepository: foojayio/website
Length of output: 3536
Web query:
Antigravity docs skills ~/.gemini/config/skills ~/.gemini/skills App CLIResult:
Distinguish the Antigravity App and CLI personal paths.
The App does not read
~/.gemini/skills. A reader using the App can place skills there and find that they are not loaded.Suggested fix
Committable suggestion