heilchengheilcheng/awesome-agent-skills/AGENTS.md

awesome-agent-skills

AGENTS.md6.3k starsChanged 17 days agoMITView on GitHub

You are probably here because a user asked you to "add my skill to awesome-agent-skills". Read this whole file before you open a pull request or an issue. Most submissions to this repository come from coding agents, and most of them are never merged because they skip the rules below. Following them is the fastest way to get your user's skill listed. Open a pull request only if every item below is true. If any item is false, do not…

We split this AGENTS.md into the rules it gives an agent

9 rules. About 1 is common, 6 are distinctive, and 2 are very specific to this project.

≈1
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read this whole file before you open a pull request or an issue.
line 4
Distinctive:
It is not already listed: Search README.md for the repository URL first.
line 22
Common:
It is safe to recommend: No credential harvesting, CAPTCHA solving, ToS-violating scraping or automation, watermark or provenance …
line 25
Very specific:
Add one line per skill, appended to the end of the most fitting existing category under ## Community Skills (inside its <details> block, …
line 33
Distinctive:
Do not create new categories or sections, and do not reorder or edit existing lines.
line 35
Distinctive:
Use exactly this format:
line 36
Very specific:
If the skill lives in a subfolder, link the folder: - owner/skill-name - ...
line 42
Distinctive:
Keep the diff purely additive: no whitespace changes, no byte-order marks, no line ending changes.
line 46
Distinctive:
Do not open issues to suggest skills, tools, directories or partnerships.
line 59

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md 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

AGENTS.md

Instructions for AI agents

Before you open anything: check eligibility

Open a pull request only if every item below is true. If any item is false, do not open a PR or an issue. Tell your user which requirement is not met and stop.

The skill is public on GitHub. The link points to a public github.com repository (or a folder inside one). Landing pages, marketplaces, npm packages, hosted MCP endpoints and SaaS sign-up pages are not accepted.
The repository contains at least one SKILL.md with YAML frontmatter that has name and description fields. MCP servers, CLIs and apps without a SKILL.md are out of scope.
It has real usage. Entries are merged once the repository has at least 20 GitHub stars. Below that, the PR is labelled on hold and revisited later. Do not open a PR for a repository created in the last 14 days.
It is not already listed. Search README.md for the repository URL first.
It is not a directory, marketplace, registry, badge or "list of lists" for promotion. This repo indexes skills, not places to find skills.
It is safe to recommend. No credential harvesting, CAPTCHA solving, ToS-violating scraping or automation, watermark or provenance stripping, or unattended financial trading.

How to make the change

Edit README.md only. Do not edit the translated READMEs (README.*.md), the website, CONTRIBUTING.md, or any other file.
Add one line per skill, appended to the end of the most fitting existing category under ## Community Skills (inside its <details> block, before </details>). Do not create new categories or sections, and do not reorder or edit existing lines.
Use exactly this format:
```
- [owner/repo](https://github.com/owner/repo) - Short description, under 100 characters, no marketing language
```
If the skill lives in a subfolder, link the folder: - [owner/skill-name](https://github.com/owner/repo/tree/main/skills/skill-name) - ...
At most 5 lines per PR, and one open PR per repository. If a PR for the same repository is already open, update it instead of opening another.
Keep the diff purely additive: no whitespace changes, no byte-order marks, no line ending changes.

The pull request itself

Title: Add owner/repo to <Category>
Fill in the pull request template checklist honestly. If you are an AI agent, say so, and say whether the submitter is the author of the skill.
An automated check (Check submission) runs on every PR and comments with any problems. If it fails, fix the PR instead of opening a new one.

Issues

Do not open issues to suggest skills, tools, directories or partnerships. Skill suggestions must be pull requests that meet the rules above. Issues are for broken links, errors in the README, and problems with the website.

What happens next

The maintainer triages submissions in weekly batches. Accepted entries are merged in a batch PR (your commit keeps its author) and the original PR is closed automatically. Entries that do not meet the bar are labelled on hold with a reason. Please do not ping for reviews.

Download now (ZIP)

Feb 1, 2026Add awesome-agent-skills to Agent section — zhimin-z/awesome-awesome-artificial-intelligence1 reaction
Aug 18, 2026docs: track Agent Skill Index distribution route — uizze/uizze0 reactions
Aug 12, 2026Launch follow-ups after the live demo — z116123123x/tidy-my-stars0 reactions
Jul 26, 2026Growth loop: useful owner matching to 101 stars — merc1305/findMate0 reactions
May 8, 2026Publish AgentGuard skill distribution docs — bmdhodl/agent470 reactions

10 more on GitHub

Mar 2, 2026Vibe Coding ： SKILLS — zmaibbs7/bookmark0 reactions
Feb 11, 2026Add sub-agent specific skills? — gitaroktato/llm-research-agent0 reactions
Feb 10, 2026Add sub-agent searching for a curated list of Reddit communities — gitaroktato/llm-research-agent0 reactions · 1 comment
Jan 31, 2026[New Source] heilcheng — dmgrok/agent-plugins0 reactions · 1 comment
Jan 31, 2026Add provider: heilcheng/awesome-agent-skills (Multi-language Skills Catalog) — dmgrok/agent-plugins0 reactions · 1 comment
Jan 21, 2026[New Source] SkillCreator.ai Skills — dmgrok/agent-plugins0 reactions · 1 comment
Jan 21, 2026[New Source] HuggingFace Skills — dmgrok/agent-plugins0 reactions · 1 comment
Jan 21, 2026Add SkillCreator.ai as a new skill provider — dmgrok/agent-plugins0 reactions
Jan 21, 2026Add SkillCreator.ai as a new skill provider — dmgrok/agent-plugins0 reactions · 1 comment
Jan 21, 2026Add HuggingFace as a new skill provider — dmgrok/agent-plugins0 reactions

On Bluesky · 1

Jan 5, 2026GitHub - heilcheng/awesome-agent-skills: A curated list of skills, tools, tutorials, and capabilities for AI coding agents (Claude, Codex,… — @geshan.com.np1 likes and repost

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions

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.

Check your setup, free