agentleFS
gmh5225gmh5225/awesome-skills/.claude/skills/overview/SKILL.md

awesome-skills-overview

Skill97 starsChanged 10 months agoMITView on GitHub

Guide for understanding and contributing to the awesome-skills curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use tables for skill listings with | Skill | Description | format.

    line 34
  2. Distinctive:

    Use full URLs in table cells.

    line 38
  3. Distinctive:

    Add a short description in the Description column.

    line 39
  4. Distinctive:

    Keep descriptions English and concise.

    line 40
  5. Distinctive:

    Do not add the same URL in multiple places.

    line 41
  6. Distinctive:

    No duplicate URLs in README.md: If a link fits multiple categories, pick the primary one.

    line 63
  7. Distinctive:

    Check for duplicates in README.md before adding.

    line 67
  8. Distinctive:

    Verify the link points to the canonical source (avoid low-value forks).

    line 68
  9. Distinctive:

    Keep the description English and useful.

    line 69
  10. Distinctive:

    Put it into the most appropriate category.

    line 70
  11. Distinctive:

    Prefer minimal changes over reformatting large sections.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Awesome Skills - Project Overview

Purpose

This is a curated collection of Agent Skills, resources, and tools for AI coding agents like Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor, and more. The goal is to keep the list high-signal, well-categorized, and non-duplicated.

Project Structure

awesome-skills/
├── README.md                # Main resource list (curated)
├── LICENSE                  # License
├── .claude/
│   └── skills/              # Claude skills (this directory)
└── ref/                     # Reference repositories (not curated)
    ├── awesome-agent-skills-*/
    ├── awesome-claude-skills-*/
    ├── awesome-codex-skills/
    ├── awesome-copilot-agents/
    └── ...

README.md Format Convention

Heading Structure

  • Top-level categories use ##.
  • Subcategories use ### (e.g., inside Community Skills).
  • Use tables for skill listings with | Skill | Description | format.

Link Format

  • Use full URLs in table cells.
  • Add a short description in the Description column.
  • Keep descriptions English and concise.
  • Do not add the same URL in multiple places.

Example Entry

### Development & Code Tools

| Skill | Description |
|-------|-------------|
| [skill-name](https://github.com/...) | Short description of the skill |

Categorization Rules (How to Place a New Link)

  • Official Skills: Skills from Anthropic, OpenAI, HuggingFace official repositories.
  • Skills by Teams: Skills from recognized teams (Vercel, Trail of Bits, Sentry, Expo).
  • Community Skills: Community-contributed skills organized by category.
  • Supporting Tools: CLI tools, installers, and management utilities.
  • Tutorials & Resources: Documentation, videos, articles, and learning materials.

Duplicate Policy

No duplicate URLs in README.md. If a link fits multiple categories, pick the primary one.

Contribution Checklist

  1. Check for duplicates in README.md before adding.
  2. Verify the link points to the canonical source (avoid low-value forks).
  3. Keep the description English and useful.
  4. Put it into the most appropriate category.
  5. Prefer minimal changes over reformatting large sections.

Full Resource List

For more detailed skill resources, complete link lists, or the latest information, use WebFetch to retrieve the full README.md:

https://raw.githubusercontent.com/gmh5225/awesome-skills/refs/heads/main/README.md

The README.md contains the complete categorized resource list with all links.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.