How to Install and Use Skills in Cursor
Right folder, right scenarios, a tidy library — 6 real Skills that make Cursor's Skills capability actually land
Deep Skill Finder
You've probably hit these walls
Installed a skill in Cursor and… nothing. No error, no log entry. It just silently ignores folders without a SKILL.md.
source: Reddit · r/cursor
Lost an hour to the Agent Skills toggle — turns out you need the Beta/Nightly channel before the option even appears in settings.
source: X · dev log
Global vs project-level skills, rules vs skills — the docs make it sound way harder than 'copy the folder, restart, done.'
source: GitHub · cursor community skills
Real voices scattered across Reddit / Hacker News / X / dev forums — stitched together, this is what people go through when doing "using skills in Cursor".
Lazy path · recommended
Install deep-skill-finder once — let your Agent find Skills for you
Whatever "using skills in Cursor" task you have, MEYO already has the matching Skills. You don't need to hunt one by one — install deep-skill-finder and your Agent will auto-search MEYO's 50,000+ Skill library on every task, recommending the best match. You just say what you want to do — matching Skills is the Agent's job.
Copy → paste into Claude Code / Codex / Cursor / WorkBuddy / CatPaw · Agent installs automatically:
Please install the deep-skill-finder skill: download the archive from https://www.meyo.life/skill-finder, extract it into your local skill directory and enable it.
Or browse common-scene Skills below. Learn more about deep-skill-finder → meyo.life/skill
Three scenes, 2 real Skills each
Install them all, or just pick 1–2 by name. Don't worry about picking wrong — they're free, uninstall anytime.
Get It Installed
Installation first — everything else comes after
For first-time Cursor skill users
clawhub-skill-finder
TOP 1
Find skills on ClawHub
Discovers and installs skills from the ClawHub public registry directly into your local skills directory
598 users
Browse a terminal-skills registry
A registry-first approach to discovering and installing agent skills from terminalskills.io
151 users
💬 Join the Deep Skill Finder Community
Trade "using skills in Cursor" workflows with other Deep Skill Finder users and get install help
FAQ
Q: What Cursor version do I need for skills?
A: Skills currently require a recent Beta/Nightly channel build, with the Agent Skills toggle enabled in settings. Stable-channel rollout may lag — check the official changelog before installing.
Q: Which folder should skills go in?
A: Global skills go in the user-level skills directory (apply to every project); project-level skills go in .cursor/skills/ (versioned with the repo, easy to share). One folder per skill, each containing a SKILL.md.
Q: Nothing happens after installing. Now what?
A: Check three things in order: the file is named SKILL.md (case-sensitive), the folder is in the right level, and Cursor has been restarted or a new session opened so it rescans the skill library.
Q: Skills vs Rules in Cursor — what's the difference?
A: Rules are always-on behavior constraints (how to work); skills are on-demand task manuals (how to do one specific thing). Standing conventions belong in Rules, reusable workflows belong in skills.
Q: What's the best way to share skills with my team?
A: Keep them in the project-level directory under version control and merge through review. Once high-frequency workflows are captured as skills, new teammates get the whole kit just by cloning the repo.
Q: How many skills should I keep installed?
A: Only what you use. Skill descriptions occupy context and participate in routing — too many dilute trigger accuracy. Keep high-frequency skills per project and tuck the rest away with a manager skill.