Browse 1,000+ Curated Agent Skills with VoltAgent's Awesome List

Most curated agent-skill lists are dumps of half-finished prompts. Awesome Agent Skills by VoltAgent is different: it catalogs 1,497+ skills from official dev teams and named publishers, each tied to a real platform (Stripe, Supabase, Anthropic, Cloudflare, and so on), so installing one teaches your agent the conventions of that platform instead of generic stubs.

Why This Skill Matters

When you ask an AI agent to write Stripe code without a skill, it invents API calls from training data — sometimes right, often a version behind. The same problem hits every platform with moving APIs: Cloudflare Workers, Supabase auth, MongoDB queries, Sentry instrumentation. A skill is a curated bundle of patterns for one platform, so the agent reasons over the right conventions.

This catalog is the place to find the right skill. VoltAgent curates for "real-world" skills versus mass AI-generated ones, and lists the publisher (Anthropic, Google, Stripe, Trail of Bits, etc.) next to each entry so you can weigh trust. The collection stays useful because most entries link to an actively maintained upstream repo rather than a hardcoded prompt.

Installation

There is no single command to install the whole collection — by design. Skills are installed one at a time:

gh skill install <owner>/<skill-name>

For example:

gh skill install stripe/agent-toolkit

Each skill's documentation lists the exact path, supported hosts (Claude Code, Codex, Gemini CLI, Cursor, GitHub Copilot, OpenCode, Windsurf), and any prerequisites. Pick by platform, not by author reputation alone — a skill can target the wrong host for your setup.

Real Workflow: Find a Skill for Your Stack

A realistic scenario: you're adding Stripe billing to a Next.js app and need the agent to produce working code instead of guessing.

1. Open the catalog on GitHub and search (or browse) for stripe.

2. Note the publisher (stripe/agent-toolkit is published by Stripe itself) and the platforms it claims to support.

3. Open the linked upstream repo. Confirm it is actively maintained, matches your SDK version, and supports your agent host.

4. Install:

   gh skill install stripe/agent-toolkit
   

5. Try a small, scoped prompt first:

   Create a Stripe Checkout session for a one-time $19 purchase and
   redirect to a success URL. Use the installed stripe skill.
   

6. Inspect the output. A skill worth installing produces concrete, idiomatic calls (the right Stripe API version, idiomatic error handling); a useless one produces a generic stub dressed up.

Expected output: a small handler that calls stripe.checkout.sessions.create(...) with the correct parameters and returns the redirect URL — not a long paragraph explaining how Stripe works.

Real Workflow: Verify the Skill Before You Trust It

Skills execute code and steer agent behavior. Before installing anything from the list, spend five minutes auditing the upstream repo:

• Stars and last commit. Recent activity beats stars alone.
• Publisher identity. Is the repo under the official org (e.g. stripe/...) or a community fork? Both are fine; know which you're getting.
• SDK version. Does the skill target the SDK you actually use? An old skill on a current SDK will give you patterns the API rejected.
• Host compatibility. Does the README list your agent (Claude Code, Cursor, Codex, etc.)?
• License. MIT, Apache, and similar open licenses are the norm here; treat anything else as a yellow flag.

Treat the install as you would an npm install of a package you've never used: read the README, skim the source, then try it on a throwaway task before relying on it in production.

Tips

• Install per-platform, not per-publisher. A skill that targets Supabase won't help with Sentry; pick by what your project actually needs.
• One skill at a time. Adding five skills at once makes it hard to tell which one helped. Install, try, then add the next.
• Pin upstream versions where possible. If a skill's repo uses tags, mirror them in your environment so a sudden upstream rewrite doesn't break your agent mid-task.
• Skim the skill's tests. Many of the better-maintained entries ship test suites — the presence of tests is a good signal.

When Not to Use This

• You need runtime access, not guidance. A skill teaches your agent patterns and conventions; it does not grant API keys or call Stripe / Cloudflare on your behalf. You still need a real account.
• You want a single install for the whole catalog. There isn't one — and that's intentional. Install per skill, per project.
• Your host isn't supported. Verify your agent (Claude Code, Codex, Cursor, etc.) is listed in the skill's compatibility matrix. A skill that only targets a different host will silently do nothing.
• You need a vendor-independent skill. Many entries are tied to specific platforms (Anthropic, Microsoft Azure, etc.). If you're deliberately avoiding a vendor, this list won't help you find a neutral alternative.

See the leaderboard for more skills.