Claude Code Skills vs Cursor Skills: Storage, Portability, and Which Wins

Claude Code skills can be saved two places: a personal folder at ~/.claude/skills/ that every project on your machine can reach, or a project folder at .claude/skills/ that ships with the repo. Cursor only has the second kind — .cursor/skills/ is project-scoped, and there is no personal or global equivalent yet, which is why Cursor's own community forum has open threads asking for one. For a solo founder juggling several SaaS repos, that's the real-world difference: one tool lets you write a skill once and reuse it everywhere, the other makes you copy the file into every repo. Last updated 2026-10-31 by Rakshit Yadav.

Where each tool actually stores a skill

Claude Code looks for skills in two places and merges what it finds: ~/.claude/skills/<name>/SKILL.md, a personal directory under your home folder that every project you open on that machine can see, and .claude/skills/<name>/SKILL.md inside the current repo, which only applies to that project and is the one you'd commit to git for teammates. Write a skill once in the personal folder — your commit-message conventions, your preferred error-handling style, a checklist you use on every repo — and it's available the next time you open Claude Code in a completely different project, no copying required.

Cursor has one folder: .cursor/skills/<name>/SKILL.md, scoped to the repo it lives in. There is no documented personal or global skills directory in Cursor as of this writing. A skill written for one Cursor project stays in that project unless you manually copy the folder somewhere else.

Side by side

Claude CodeCursor
Personal / cross-project folder~/.claude/skills/ — yesNone documented
Project folder.claude/skills/.cursor/skills/
Reuse across repos without copyingYes, via the personal folderNo — copy the folder into each repo
Committed, shared with teammatesProject-folder skills, yesProject-folder skills, yes
FormatYAML frontmatter (name, description) + markdown bodySame shape

Why Cursor doesn't have a personal skills folder yet

Cursor's skill format closely tracks the SKILL.md convention Anthropic introduced for Claude, and Cursor's own community forum has open, unresolved threads from users asking whether Cursor plans a global or personal skills directory the way Claude Code has one — the requests are visible on forum.cursor.com but there's no shipped feature or confirmed roadmap date to point to as of 2026-10-31. Until that lands, every Cursor skill is tied to the repo it was written in, full stop.

The copy-paste workaround

Because SKILL.md's content — the markdown body with its instructions, examples and gotchas — doesn't reference any tool-specific path, the practical workaround for Cursor users is a manual one: keep a personal library of SKILL.md files outside any single repo (a dotfiles repo, a gist, a local folder), and copy the ones you need into .cursor/skills/ at the start of each new project. It's not automatic reuse, but it means you're not rewriting the same conventions file from scratch for every repo. Claude Code users get the same outcome natively through ~/.claude/skills/, with no copy step at all.

Verdict: when a solo SaaS founder should centralize in Claude Code

If you run more than one or two repos — a SaaS app, a marketing site, a couple of client projects — and you keep rewriting the same skill (how you want errors handled, how you want PRs described, your testing conventions) in each one, Claude Code's personal skills folder removes that duplication outright: write it once in ~/.claude/skills/, use it everywhere. If you work in a single repo most of the time and only occasionally start a new one, the gap matters less — a one-time copy into .cursor/skills/ costs you a minute. The project-scoped folder itself is identical in both tools and works equally well for the conventions that are genuinely repo-specific, like a particular API's quirks; it's cross-repo, personal knowledge where Claude Code currently has the structural edge.

Related pages

Frequently asked questions

  • Does Cursor have a personal or global skills folder like ~/.claude/skills/?
    Not as of 2026-10-31. Cursor skills live only in .cursor/skills/ inside each project. There are open requests on Cursor's community forum asking for a personal/global equivalent, but no shipped feature to point to yet.
  • Can I reuse the same skill across multiple Cursor projects?
    Not automatically. You'd copy the SKILL.md file (or the whole folder) from one project's .cursor/skills/ into another's. Claude Code avoids this by also supporting a personal folder at ~/.claude/skills/ that every project reads.
  • Is a Claude Code personal skill shared with teammates automatically?
    No — ~/.claude/skills/ is local to your machine and isn't committed to the repo. For skills teammates need, put them in the project's .claude/skills/ and commit that folder; keep ~/.claude/skills/ for your own cross-project habits.
  • Does the SKILL.md content itself need to change between Cursor and Claude Code?
    Usually not — the markdown body (instructions, examples, gotchas) is tool-agnostic. Only the folder path and any tool-specific references (a named Cursor rule, a named Claude Code subagent) need adjusting when you move a skill between the two.
  • Which should a solo founder running both Cursor and Claude Code pick?
    Keep instructional skill bodies tool-agnostic so the same content can live in both .cursor/skills/ and .claude/skills/. Use Claude Code's ~/.claude/skills/ for anything genuinely cross-project and personal, since Cursor has no equivalent yet.

Centralize your skills in Claude Code

AgenticKit installs a skill set your agents and commands already reference by name, so you're not hand-copying SKILL.md files between repos.