Claude skills are genuinely useful. For most of the people who would benefit from them most, they are also genuinely inaccessible. Discovering them means trawling GitHub repositories. Installing them means editing config files. Anyone who is not a developer encounters a wall before they ever see what the skill actually does.
Patrick McDougall built his Claude skills discovery tool to remove that wall. The problem he identified was not that skills were obscure - it was that the gap between "this skill exists" and "this skill is running in Claude" was too wide for anyone without a technical background to cross comfortably.
The tool brings the entire experience closer to an app store. Skills are browsable in a structured interface. Installing one takes a couple of clicks rather than cloning a repository and manually editing a configuration file. The person who could benefit most from Claude productivity skills - the non-developer who uses Claude heavily but has never opened a terminal - can now actually use them.
UX as the Core Differentiator
Patrick is direct about what makes his approach different from other attempts at Claude skill discovery: the others are essentially well-formatted lists of links. His focus was on making the browsing and installation experience feel native rather than technical. Finding a skill feels like finding an app. Adding it feels like installing one.
The target user is non-technical Claude users first - the people who would get the most value from skills but currently have no realistic path to them. As Claude's ecosystem of skills grows, the need for a navigable, install-friendly layer becomes more significant, not less.
