Documentation

AAS Core with Claude Code

For Claude Code, the recommended AAS path is AAS Core: a local, agent-first control plane for complete catalog search, Claude-owned skill selection, manifest inspection, and preview-first planning.

The local AAS MCP is read-only. It lets Claude search and read every catalog skill, then validate and pin Claude's chosen IDs in aas-stack.json; planning and any approved changes stay in the AAS CLI lifecycle.

Start with the AAS Core guide. The Claude plugin marketplace and direct skill installation remain supported delivery paths after you know which skills you want.

Preview status: Complete catalog search, agent-owned selection, manifest validation, and planning are the documented path. Stop after plan review; apply and recovery remain experimental.

How to use Agentic Awesome Skills with Claude Code

Configure AAS Core for Claude Code, describe the task and constraints, let Claude choose exact IDs from the complete catalog, then review the composed stack and preview the CLI plan. Core does not install or mutate through MCP.

Why use this repo for Claude Code

Direct install and plugins

These are alternative delivery paths for users who already know which skill payload they want.

Option A: installer CLI

npx agentic-awesome-skills --claude

Option B: Claude Code plugin marketplace

/plugin marketplace add sickn33/agentic-awesome-skills
/plugin install agentic-awesome-skills

The Claude marketplace plugin is a plugin-safe filtered distribution of the repo. Skills that still require portability hardening or explicit setup metadata remain available in the repository, but are excluded from the plugin until they are ready.

You can also install a focused bundle plugin instead of the root plugin when you want a narrower starter surface. See plugins.md and bundles.md.

Verify the install

test -d .claude/skills || test -d ~/.claude/skills

Best starter skills for Claude Code

Example Claude Code prompts

With AAS Core configured:

Inspect this security-review project, search and read the complete AAS catalog, and choose the exact skill IDs you judge most useful. Use compose_stack with a project profile, show me the schema 2 aas-stack.json, inspect it, and preview the plan without applying it.

After installing or activating a chosen skill, direct invocation still works:

Use @brainstorming to design a new billing workflow for my SaaS.
Use @lint-and-validate on src/routes/api.ts and fix the issues you find.
Use @create-pr to turn these changes into a clean PR summary and checklist.

What to do next