# Agentic Awesome Skills vs Awesome Claude Skills

If you are comparing **Agentic Awesome Skills** with **Awesome Claude Skills**, first decide whether you need complete catalog access with agent-owned reproducible selection or an editorial discovery list.

For clarity: the repository many people still refer to as `awesome-claude-skills` now lives at [VoltAgent/awesome-agent-skills](https://github.com/VoltAgent/awesome-agent-skills).

## TL;DR

- Choose **Agentic Awesome Skills** if you want AAS Core to turn an explicit project profile into an explainable, reviewable skill stack, with broad catalog and distribution support around it.
- Choose **VoltAgent Awesome Agent Skills** if you want a curated list with a strong official-team angle and a tighter scope.

## At-a-glance comparison

| Criteria | Agentic Awesome Skills | VoltAgent Awesome Agent Skills |
| --- | --- | --- |
| Best for | Complete local catalog access, agent-owned selection, durable desired state, and plan preview | Curated discovery and official/community highlights |
| Product shape | AAS Core with local MCP, CLI, stack/plan artifacts, Workbench review, and supporting catalog/distribution | Curated awesome-list style collection |
| Supported tools | Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, Kiro, OpenCode, Copilot, more | Claude Code, Codex, Antigravity, Gemini CLI, Cursor, Copilot, OpenCode, Windsurf, more |
| Onboarding | Installation docs, bundles, workflows, getting-started guides | Curated README and categorized references |
| Good fit when | You want an agent to inspect a project and choose exact IDs from the full catalog | You want a smaller list to browse and evaluate manually |

## Why choose Agentic Awesome Skills

- You want Codex or Claude to search and read a complete catalog through a local, read-only MCP and own the selection.
- You want the approved selection recorded as `aas-stack.json` and validated before an immutable plan is produced.
- You care about onboarding assets like [`bundles.md`](bundles.md), [`workflows.md`](workflows.md), and tool-specific guides.
- You need coverage across many domains, not just a curated shortlist.

## Why choose VoltAgent Awesome Agent Skills

- You want a more editorial, awesome-list style browsing experience.
- You value a repository centered on official and team-published agent skills.
- You prefer a smaller set to review manually before installing anything.

## Honest tradeoffs

- The AAS catalog is larger and its evidence remains uneven; Core reports unknowns rather than treating breadth as certified quality.
- VoltAgent can be easier to skim quickly because it optimizes for curation.
- If you want both, use curated lists for editorial discovery and AAS Core when you need a reproducible agent-selected project stack.

## Suggested next step

- If you want project-specific composition, start with the [AAS Core guide](aas-core.md). If you already know exact skill IDs, use the direct distribution options in [`README.md`](../../README.md).
- If you are still evaluating tool-specific options, continue with [`best-claude-code-skills-github.md`](best-claude-code-skills-github.md) or [`best-cursor-skills-github.md`](best-cursor-skills-github.md).