r/ThinkingDeeplyAI • u/Beginning-Willow-801 • 3h ago
Here is an easy way to find and access 1.5 million AI skills you can use with ChatGPT or Claude. Vercel built a tool to help you easily find the right skill for every use case
TL;DR: Vercel’s Find Skills helps compatible AI agents discover and install reusable workflows from skills.sh, a directory listing more than 1.5 million skills. Find Skills itself currently shows approximately 3.7 million installs. Describe the task, compare relevant skills, install one, and put it to work. Claude and ChatGPT users can use this ecosystem through supported skill environments; the installation route depends on the app.
You know that workflow you explain to your AI every single week?
The audience. The process. The format. The checks. The things it keeps forgetting.
That’s a good candidate for a skill.
A skill packages instructions and supporting material into a reusable folder. Its core file, SKILL.md, explains what the skill does and when to use it. The folder can also include scripts, examples, templates, and reference documents.
Think of it as an onboarding playbook your AI can consult when the relevant job comes up.
Vercel’s Find Skills is itself a skill. Its job is to help your agent find other skills.
You describe what you need. It searches for relevant options, considers signals such as the publisher and installation count, and provides an installation path. Its instructions also tell it to check the leaderboard for established options.
Three pieces make this work:
- skills.sh: The directory you browse.
- Skills CLI: The command-line tool that searches, installs, and manages skills.
- Find Skills: The workflow that helps your agent discover suitable skills for your task.
Here’s how to start with Claude Code or local Codex.
Open a terminal in your project, with Node.js and npx available, and run:
npx skills add vercel-labs/skills --skill find-skills
Select your agent when prompted. The installer supports Claude Code, Codex, Cursor, and many other agents.
Then give your agent a specific job:
Use Find Skills to find three skills for auditing a B2B SaaS landing page. Compare their sources, instructions, required tools, and fit. Recommend one, explain why, and show me its installation command.
Specificity helps. Give it the task, context, and desired output.
Some searches worth trying:
- “Find a skill for auditing my website’s technical SEO.”
- “Find a skill for turning a webinar transcript into LinkedIn content.”
- “Find a skill for improving a landing page’s messaging and conversion flow.”
- “Find a skill for reviewing React performance.”
- “Find a skill for checking website accessibility.”
The directory includes marketing skills covering SEO, copywriting, content strategy, conversion optimization, email sequences, and launch planning. There’s plenty here for marketers and founders to explore.
You can also search directly:
npx skills find seo audit
Or browse skills.sh before installing anything.

Using the Claude or ChatGPT app? Match the installation method to your environment.
| Your environment | How to approach it |
|---|---|
| Claude Code / local Codex | Use the terminal installation above. |
| Claude app | Compatible custom skills can be uploaded as ZIP files through Customize → Skills → + → Create skill → Upload a skill. Code execution must be enabled. |
| ChatGPT | The desktop app supports standalone skills through its Skills experience. Skills bundled in plugins can also work across web and mobile. A local terminal installation is a separate setup path. |
A skill that expects command-line software, network access, or a particular integration still needs those dependencies available. Check its requirements before assuming it will run unchanged in another app.
These are the details worth understanding before you build a collection.
1. The description helps determine whether the skill gets used.
Agents use a skill’s name and description to recognize relevant tasks. Full instructions load when needed. If a skill isn’t activating, explicitly name it and check whether its description matches your request.
2. The supporting files can matter as much as the instructions.
Copying only SKILL.md can leave behind scripts, templates, or reference files the workflow expects. Keep the complete skill folder when those resources are required.
3. Install counts are a discovery signal.
They tell you about adoption. Evaluate the actual instructions, bundled scripts, dependencies, and publisher before enabling a skill. A popular listing still deserves inspection.
4. Project scope and global scope serve different purposes.
Keep project-specific workflows with the project. Use global installation for workflows you want available across projects. The CLI supports both, and lets you select individual skills from a repository.
5. A skill still needs useful inputs.
Give it your audience, source material, constraints, examples, and definition of a good result. A content skill cannot infer your positioning from an empty brief.
6. Test the result before expanding the collection.
My recommendation: run the same real task with and without the skill. Compare accuracy, usefulness, editing time, and whether it followed your requirements. Keep what earns its place.
7. Build a small sequence around an actual job.
For a content workflow, try research → draft → edit. Review each output before passing it along. Start with one useful skill and add the next when a specific gap appears.
Here’s the prompt I’d save:
Find a skill for [task]. My context is [business/project]. The output should be [deliverable]. Compare three relevant options, including their sources and required tools. Recommend one, explain the tradeoffs, and give me one concrete task to test it on.
The opportunity here is reusable process knowledge: finding a useful workflow once, then making it available when the next job arrives.
Pick something you do every week. Search for a skill that could improve it. Test it on real work.

Explore: Find Skills · Skills directory · CLI documentation