There are thousands of agent skills. They live in dozens of repositories, in at least six different directory conventions, under licenses that are usually unstated. Finding one is easy. Knowing whether it still works, who wrote it, and what you're allowed to do with it is not.

Aidentity is a registry. Each entry is one record with a stable ID, an upstream source, an author, a license, a status, and the date it was last verified. The website, the CLI, and the machine-readable registry all read the same file.

Verification

Every Monday, CI requests each upstream repository. The result is written to registry/verified.json and rendered on every page that depends on it. If a source disappears, an issue is opened automatically. A stale link is a bug, not an accepted cost.

Licensing

Three rules:

1. Content is mirrored only when the upstream license permits redistribution (MIT, Apache-2.0).
2. When it does not, the entry is a pointer: name, description, author, license, upstream URL. No content.
3. Every mirrored source keeps its upstream LICENSE file. Notices are generated, not hand-written.

This repository's own code is MIT. The registry data is CC0. Original writing is CC BY 4.0. Vendored skills remain under their upstream licenses.

Machine-readable

The registry is a single JSON file, versioned and schema-validated. Agents can read it directly: registry.json · llms.txt · sitemap.xml.

Questions

What is Aidentity?

Aidentity is a verified index of 526 AI agent skills. Each entry records its source repository, author, license, category and last verification date. You install any hosted skill with one command.

Are the skills free to use?

Most are MIT or Apache-2.0. Trail of Bits skills are CC BY-SA 4.0. 19 skills from Anthropic are indexed with a link only, because their upstream license does not permit redistribution. Every page states its license.

How do I install one?

Run npx aidentity add <id>, or copy the folder from skills/<source>/<name>/. The CLI detects Claude Code, Cursor, Codex, Gemini CLI, OpenCode or Copilot and writes to the right directory.

How do you keep the index accurate?

CI rebuilds the registry on every change and checks the license policy. A weekly job requests every upstream repository, writes the result to registry/verified.json and opens a report PR when something is unreachable.

Can I add a skill?

Yes. One JSON record and a pull request. CI validates the schema, the license and that the source resolves. See the contributing guide.

Contributing

One JSON record per pull request. CI validates the schema, the license, and that the source resolves. Maintainers review within a day.

Contributing guide ↗