Yesterday a Reddit post quietly dropped that solved a problem I didn’t realize I had until I tried switching computers.
Someone lost 1,200+ Claude skills when they changed machines. Couldn’t find half of them again. Bookmarks gone, GitHub tabs closed, links dead. Think about what that actually means: months of curating the exact prompts that made your workflow click, gone because nobody thought to back up a browser tab. Skills for writing, for debugging, for turning a raw data dump into something a client can actually read. All of it, scattered across a browser history nobody exports until it’s too late.
So they built a searchable directory instead. That’s the twist: this thing exists because of a painful personal failure, not a grand plan. No VC pitch. No product roadmap. Just someone who got burned and decided to fix the problem properly.
The tool: PromptCreek Skills Directory
Free. No signup. No email wall. You just… use it.
What makes this different from the usual GitHub gist graveyard is the organization. Most skill repositories are basically a pile of text files with a README that hasn’t been updated since the initial commit. You’re hunting through folders named “misc” and “other,” trying to remember which file had the SQL query formatter you used six months ago. PromptCreek treats skills like software: categorized, searchable, and installable. That’s a higher standard than most people bother to set, and it shows in how quickly you can actually find what you came for.
Here’s how it works in practice:
- 🔍 Go to promptcreek.com/skills. The homepage loads fast and the search bar is front and center. No dark patterns, no “start your free trial” modal blocking the content. The directory is the product, full stop.
- 📂 Browse by category (Engineering, Marketing, Productivity, Sales, Finance, Data) or search by keyword for exactly what you need. The categories are broad enough to be useful and specific enough to mean something. If you’re a developer, Engineering is your starting point. Running campaigns? Marketing has skills for copywriting, competitor research, and positioning frameworks. Productivity covers the generalist stuff: summarization, meeting prep, weekly planning. The keyword search is fast and doesn’t require you to already know the name of the thing you’re looking for.
- 📋 Copy the skill straight into Claude, or install it via a single terminal command. Both options work. The copy-paste route is fine for one-off use. The terminal install is the move if you’re building a library you’ll actually maintain beyond this week.
- ✅ Done. No friction. No account, no OAuth dance, no “invite a friend to unlock.” You searched, you found, you installed. That’s the entire loop.
The engineering section alone is worth bookmarking: code review, debugging, test generation, refactoring. All organized by what you’re actually trying to do, not by who submitted it or when. The code review skill, for example, isn’t just “review my code” wrapped in a system prompt. It’s structured to surface specific issue types: logic errors, edge cases, security concerns. The debugging skills walk Claude through systematic isolation rather than just asking it to guess. That kind of structure is what separates a skill that actually improves your output from one that’s just a fancy way to type a question.
Pro tip: The terminal install command is underrated. One line and the skill is in your setup. The community already noticed this is cleaner than the usual copy-paste-and-hope workflow. But here’s what I’d add on top: once you install a few skills this way, name them something consistent. Skills named “skill-1” and “imported-cr-v2” will haunt you in three months when you can’t remember which is which. Spend thirty seconds on the name. Also worth doing: keep a plain text file, a Notion page, whatever works for you, with the five or six skills you reach for constantly. The directory is great for discovery. Your own shortlist is what you need at 11pm when a deadline is closing in and you don’t want to search for anything.
🚀 If you’ve got a folder of random Claude prompts you can never find when you need them, this is the fix. Try it at promptcreek.com/skills and drop a comment there if there’s a use case category missing. The categories they’ve built cover a solid range, but there’s always a niche workflow that doesn’t fit neatly into Marketing or Engineering. If yours is one of them, say something. The person who built this solved their own problem by building in public. They’re probably paying attention.
I organized 1,200+ Claude skills by use case into a free, searchable directory
by u/Big-Initiative-4256 in PromptEngineering