Aug 27, 2026

awesome-agent-skills: An Annotated Cross-Agent Skills Index

A 6k-star curated list that pairs a beginner-friendly primer on agent skills with a vendor-by-vendor directory of the Anthropic, OpenAI, Google, Hugging Face, Replicate, fal.ai, Vercel, Stripe, and Trail of Bits skills people actually use.

#tutorial#skill-management#developer-tools#claude-code

Most awesome-list repos assume you already know what agent skills are and just want a dump of links. heilcheng/awesome-agent-skills opens the other way around: it begins with a beginner primer, then walks through compatible agents, official vendor directories, community collections, skill quality standards, and a FAQ before listing the resources themselves. If you are new to skills, this is the index that explains itself as it goes.

Why This Skill Matters

The README's table of contents is split between explanatory sections (What Are Agent Skills, How to Find Skills, Compatible Agents, Skill Quality Standards, Using Skills, Creating Skills, Frequently Asked Questions) and the actual directory listings (Official Skill Directories, Community Skills, Official Tutorials and Guides, Trends & Capabilities 2026). A "Quick Start (30 seconds)" callout at the top names three steps. An inline tip recommends the SkillsMP Marketplace as the search engine. The README explicitly notes it focuses on real-world skills from actual engineering teams rather than bulk-generated skill dumps.

The vendor section alone is substantial. The README breaks it into six sub-areas (AI Platforms & Models, Cloud & Infrastructure, Developer Tools & Frameworks, Google Ecosystem, Business/Productivity/Marketing, Security & Web Intelligence) with named skill groupings per vendor (Anthropic: 16 entries; OpenAI Codex: 18; Google Gemini: 4; Hugging Face: 4; Replicate: 1; fal.ai: 3; Vercel: 5; Cloudflare: 6; Netlify: 6; HashiCorp: 6; Trail of Bits: 4; Sentry: 3; Microsoft: 5; and many more). Compatible agents are enumerated up front: Claude Code, Claude.ai, Codex, GitHub Copilot, VS Code, Antigravity, Kiro, Gemini CLI, Junie.

For someone deciding what to install, this is the index that explains the conceptual landscape first and only then links to the artefacts.

Installation

This is a curated list, not an installable plugin. Clone or browse the README; the install commands live inside the entries themselves.

git clone https://github.com/heilcheng/awesome-agent-skills

The README documents a few generic install paths:

# Find skills by query
npx skills find [query]

# Add a skill
npx skills add <owner/repo>

# List, check, update, remove
npx skills list
npx skills check
npx skills update
npx skills remove [skill-name]

For Claude Code specifically, the README also lists the directory-based approach:

mkdir -p ~/.claude/skills/
cp -r skill-name ~/.claude/skills/

The Codex entries reference $skill-creator and $skill-installer slash commands. License is MIT.

Real Workflow: Pick a Skill for Your Agent From a Vendor Sub-Area

You are setting up Claude Code for a small Next.js + Stripe team and want one skill for Stripe integration and one for Vercel deployment. Rather than searching GitHub, you can scan the vendor directory in one place.

Step 1. Open the README and jump to Official Skill Directories → Developer Tools & Frameworks → Vercel. The README lists Vercel skills (5 entries) with one-line descriptions.

Step 2. Click into the Vercel entry that best matches your need (deploy-preview troubleshooting, env-var management, or build-cache debugging). Each entry links to its upstream repo.

Step 3. From the same directory, jump to Business, Productivity & Marketing → Stripe (2 entries). Pick the one that matches the job — for example, a test-clock helper vs. a subscription-debug skill.

Step 4. Install both into your project:

npx skills add <vercel-skill-owner>/<vercel-skill>
npx skills add <stripe-skill-owner>/<stripe-skill>

Step 5. Verify they show up in your agent's installed list, then invoke one end-to-end. The README's enumeration is a starting point; install and test before adopting.

Real Workflow: Use the Quality Standards Section Before Adopting Anything

The README includes a dedicated Skill Quality Standards section and a FAQ with 9 questions. Use them as a vetting checklist before installing anything from the directory.

Step 1. Open the Quality Standards section. Note the criteria the README highlights (the section explains what separates a maintained skill from a bulk-generated one — worth reading rather than assuming any entry passes the bar).

Step 2. Open the FAQ. The 9 questions cover common confusion points (how Skills differ from slash commands and MCP servers, what counts as a Skill vs a prompt, where to find them).

Step 3. For the two skills you picked in the previous workflow, run through the FAQ's checklist mentally: does the upstream README explain when to use and when not to use the skill? Is there a SKILL.md with trigger conditions? Is the upstream repo recently active?

Step 4. Only install skills that pass the check. Use the README's curated list as a discovery layer; do your own vetting before installing. The same tip appears on each entry's "find" path: search, click through, verify, install.

Tips

  • Start with the primer sections (What Are Agent Skills, How to Find Skills) if you are new to skills — they explain the conceptual model before the directory listings.
  • Use the Compatible Agents section to confirm your agent supports the skill format before installing.
  • Treat the Vendor directory as a starting point: the entries are curated, but verify on the upstream side before installing.
  • Read the FAQ and the Quality Standards sections before adopting anything — both are short and save you from the bulk-generated skill trap the README warns about.
  • The README ships five translation files (Chinese Simplified, Chinese Traditional, Japanese, Korean, Spanish) which make it useful for non-English readers; if your audience includes them, link to the translation that matches.

When Not to Use This

If you already have a specific skill's repo URL and want to install directly, skip this list and use the CLI tool. The list adds value when you are deciding what to install or learning what skills exist; it does not add value when the question is already answered. Also, the list does not auto-update — entries drift if upstream repos move or disappear, so always check the upstream README before installing.


See the leaderboard for more curated agent skill indexes.