Windsurf is a real search topic, but the current inventory is not strong enough to justify a dedicated collection page yet. A guide is the better format for now because it can point you to the collections that already have stronger coverage and better examples.
That is not a compromise. It is a cleaner match to search behavior. Users searching for Windsurf skills usually want to know which reusable workflows transfer well, how Cascade-style interactions relate to skills, and where to find concrete examples without reading dozens of unrelated repositories.
Look for skills that are:
Those three filters matter more than the brand name alone. Today, the strongest substitutes for a thin Windsurf-only directory are the Claude Code collection, Browser Automation skills, and GitHub skills. They capture the kinds of workflows Windsurf users are often trying to accelerate anyway.
If you want concrete detail pages to open next, start with:
These are useful because they encode repeatable execution patterns. One focuses on computer-use style orchestration, one on repository workflow, and one on browser-driven validation. Together they approximate the sort of practical skill stack Windsurf searchers usually want.
Windsurf users may search with "Cascade" language instead of "skills" language. That is another reason a guide helps here. It can connect those two vocabularies more naturally and still point you toward concrete skills to inspect.
The best pattern is to treat the guide as the term-bridging layer and the collections as the browsing layer. If you need official context on the product, start with the Windsurf documentation, then use this site to compare reusable workflow packages rather than runtime marketing pages.
After this guide, browse Claude Code skills if your work is coding-heavy, GitHub skills if your bottleneck is repository operations, or Browser Automation skills if you care about end-to-end testing and validation.