DEV Community

Howie54023
Howie54023

Posted on

I Built a Skill Directory for AI Agents. Here is Why.

This is the first project I built while experimenting with vibe coding.

It is a structured directory of AI agent skills — not because there are not enough tools, but because there is not enough structure.

The gap I kept running into

While using Claude and Cursor intensively, I noticed a specific gap. When I know what capability I need, I can search for it. But when I do not know what is possible, discovery becomes random. Many powerful skills are found accidentally rather than intentionally.

Capability growth is accelerating. Awareness growth is not. That asymmetry compounds over time.

How skills are discovered today

Today, skills are discovered through GitHub repositories, Discord communities, documentation, rankings, and social feeds. There is no shortage of information. What is missing is organization.

Most platforms optimize for search. Few optimize for browsing. Search solves tasks; browsing builds capability boundaries. They serve different cognitive functions, yet the ecosystem mostly optimizes the former.

This project is an attempt to address the latter.

Two structural decisions

Two decisions shaped the design. First, organize by role rather than by technical taxonomy. Second, prioritize browsing paths over deep search features. Not as a differentiation tactic, but as a reflection of how work actually happens. Most people think in roles and workflows, not in protocol layers.

Why web instead of an app?

Skill usage happens on desktop — inside IDEs, terminals, and browsers. This is workflow infrastructure, not idle consumption. Apps optimize for distribution; the web optimizes for structure and indexability. For a directory, structure matters more than push notifications.

If you are curious, the project is here: discoveraiskills.com

What is next

Next steps include publishing curated skill collections, expanding data sources, reducing UX friction, strengthening SEO foundations, and gradually introducing UGC. There is no rush. Capability maps built too quickly tend to collapse into tool dumps.

If I had to reduce it to one line:

AI can search for you. It cannot build your capability map.

That still requires intent. This project is simply an attempt to make that map easier to see.

Top comments (0)