Question 1

What is an agent skill?

Accepted Answer

A folder of instructions, and sometimes scripts, that an AI coding agent loads to do a specific job — write an llms.txt, audit redirects, pull a Search Console report. You install one with a single command and the agent follows it from then on.

Question 2

Where does this list come from?

Accepted Answer

From skills.sh, through its documented API, read every fortnight. Install counts and security audits are theirs, shown as they were at the last sync and linked back on every row. Which shelf a skill sits on is ours.

Question 3

Why are these categories not the ones on skills.sh?

Accepted Answer

Because their API has no category filter at all, and the topics on their pages are a developer's shelves — React, databases, testing. A marketer looking for something that makes their pages retrievable is not helped by either, so we read each skill once and file it under the work it does.

Question 4

What does the trend column mean?

Accepted Answer

The change in install count since the first time we read that skill. The directory publishes today's number; we keep every number we have taken, so the shape of the climb exists here and nowhere else. A skill read once says so rather than showing a change of zero.

Question 5

Is a skill with no audit unsafe?

Accepted Answer

No — it is unaudited, which is a different fact. The directory generates an audit after a skill's first install, so an empty cell usually means the skill is new or rarely installed. Hovering a verdict names every auditor and what each one said.

Question 6

Do you host the skills?

Accepted Answer

No. A skill belongs to its author under the licence in their repository. We show a name, a shape, a count and a link; installing happens on the directory or in the repository, never here.

Question 7

What skills should I install for SEO work?

Accepted Answer

Start from the Technical SEO shelf here, sorted by installs: a skill thousands of people run is one whose failure modes are known. Check the audit column before you install anything that will run scripts, and prefer one with more than one auditor behind its verdict.

Question 8

Is there a skill that writes llms.txt?

Accepted Answer

Yes, and it is one of the most installed things on the GEO shelf. The skill reads a sitemap, ranks the pages worth naming to an assistant and keeps the file in step with the build — which is the part that usually rots when somebody writes one by hand.

Question 9

Which of these is actually growing?

Accepted Answer

The trend column answers that, and it is the only column here a live leaderboard cannot show you: it compares today's count with what we recorded a fortnight ago. A skill climbing steeply is a job enough teams have that somebody bothered to automate it.

Question 10

Can I trust a skill from a repository I have never heard of?

Accepted Answer

Read the audit column first: it reports what independent security vendors found in the skill's own files. Then open the skill's page — the file list shows how big the thing is and what it carries, and the link goes to the repository where you can read it yourself before running it.

plan-orchestrate

Installfrom the directory

What is inside itfrom the directory

What the auditors foundfrom the directory

Installs, reading by readingours

Filed alongside itours