Cursor Skills Guide

Cursor now has a dedicated platform page on this site: Cursor skills. This guide is not a replacement for that collection. It is the companion page for users who are trying to understand how Cursor-oriented skills fit next to rules, commands, and broader workflow reuse.

Use the platform page for browsing

If your immediate need is a list, go to the Cursor platform collection. That page is the main place to browse. This guide exists for the next layer: how to search, how to compare skills with rules, and how to decide whether a skill is truly useful in Cursor-driven work.

What makes a skill useful in Cursor

The best Cursor-oriented skills usually:

1. encode repeatable engineering work
2. make outputs explicit
3. avoid hiding important assumptions in vague helper text

That means platform branding alone is not enough. A strong skill can still be valuable in Cursor even if its metadata emphasizes the workflow first, not the product name.

Cursor rules are adjacent, not identical

Cursor users often search for both skills and rules because they solve nearby problems. Rules are good for persistent behavior and project conventions. Skills are better for reusable, invoked workflows with clearer task boundaries.

If you want the side-by-side framing, continue with Cursor rules vs skills.

Next steps

Use the Cursor platform collection for browsing, then compare related workflows in Browser Automation skills, GitHub skills, and Vercel skills.