ai-registry

Name: ai-registry
Author: atlanai

Pending

An open standard for AI registries

58stars

1forks

TypeScript

Installation

# Add to your Claude Code skills
git clone https://github.com/atlanai/ai-registry

Getting Started

Guides for using ai agents skills like ai-registry.

Caveman: Cut Claude Token Use by 65%
How agent-side prompt compression works, when to use it, and when not to.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.
Getting Started with AI Skills

Compare with similar skills

See how ai-registry compares with popular alternatives.

ai-registry vs rea

See comparison

README.md

Frequently Asked Questions

What is ai-registry?

ai-registry is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by atlanai. An open standard for AI registries. It has 58 GitHub stars.

Is ai-registry safe to use?

ai-registry's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.

How do I install ai-registry?

Clone the repository with "git clone https://github.com/atlanai/ai-registry" and add it to your Claude Code skills directory (see the Installation section above).

What programming language is ai-registry written in?

ai-registry is primarily written in TypeScript. It is open-source under atlanai on GitHub, so you can review or fork the full source.

Are there alternatives to ai-registry?

Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ai-registry against similar tools.

AI Courses · Agentic AI, LLM Engineering & MCP

Beginner to professional · First lesson free · Lifetime access

20% off

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

rea

by morluto

Reverse engineer anything with agents, from app behavior down to native binaries.

386,883

ai-landing-consultant brow

⚠️ Third-Party Software Notice

This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.

Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.

Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.

Read the Terms of Service

What is ai-registry?

An agent registry stores your organization's AI artifacts and manages their lifecycle. It's the source of truth for the skills and agents your teams share, so everyone works from the same verified version of each skill and agent, no matter what team they're on or harness they use. However, registries today are often tied to one ecosystem or one vendor's storage, so only that vendor's tools can read your artifacts, and moving them means a migration.

ai-registry is an open standard that enables anyone to build an open, interoperable agent registry.

Open format: Today each registry, and each coding agent's own store, has its own format for versions, ownership and approvals, so every client needs a connector per registry. With an open specification, a client integrates once, reads any registry that implements it, and installs into any downstream harness.
Open storage: Today a registry is tied to its own storage, so its records can only be read through that registry's software. With an open specification, a registry is just a set of files in a defined layout, so you can build one on infrastructure you already have, such as a git repository or an object storage bucket. The aireg CLI reads registries in folders and git repositories today.

Why not just a git repository of skills, or a plugin marketplace?

In a plain repository of skills or a marketplace, everyone gets whatever copy is there when they install, so teammates end up running different copies, and nobody can tell which. A registry can live in a git repository too, but it pins and verifies every version, gives every machine identical bytes, rolls back or yanks a version for everyone, and keeps all your harnesses in sync from one record.

Get started

The easiest way to get started is to follow the Quickstart.

To have your coding agent set up ai-registry for you, paste this prompt into Claude Code, Codex or Cursor:

Set me up with ai-registry: https://github.com/atlanai/ai-registry

The agent follows the setup skill in this repository, skills/ai-registry/SKILL.md. It asks before it installs aireg and the aireg skills, offers to try the example registry, then helps you set up a registry for yourself or your team. The use cases have more prompts to try, from your own coding agents to a whole team.

Install the aireg CLI on macOS or Linux:

curl -fsSL https://aireg.sh/install | sh

On Windows, run this in PowerShell:

irm https://aireg.sh/install.ps1 | iex

Check the installation with aireg --version. To read the install script first, or to install a specific release, see Install the aireg CLI. To run aireg from source, see CONTRIBUTING.md.

Then install the skills and agents from the example registry in this repository into a new project:

mkdir try-aireg && cd try-aireg && git init
aireg registry add github.com/atlanai/ai-registry --path examples/acme-registry
aireg add acme/engineering
aireg list

aireg links them into the folders your coding agents read, and records each exact version in .registry/manifest.lock.yml. aireg add also installs from a plugin marketplace, a site's Agent Skills index, or a folder or repository of skills; see aireg add.

When it runs in a terminal, the installer offers the aireg skills, from the release it installs. They let your coding agent set up, install from and publish to registries for you. To add them later:

aireg registry add github.com/atlanai/ai-registry --path examples/aireg -g
aireg add ai-registry/aireg -g

Roadmap

The ai-registry project currently includes:

Registry file spec. The specification you can use to implement an agent registry, with its JSON Schemas.
aireg. A CLI client for the specification that creates registries, publishes to them and installs from them into Claude Code, Codex and Cursor.
Example registries and checks you can use to verify a registry against the spec.

The spec is a draft (v0.1) and aireg hasn't reached 1.0, so both may still make breaking changes. We plan to add a catalog API for creating, federating and governing registries, and an MCP server that lets an agent read a registry directly.

Contributing

Start with CONTRIBUTING.md, which covers bug reports, spec changes and setting up the CLI. Coding agents should read AGENTS.md.

Everyone taking part follows the Code of Conduct. Report security issues privately, as described in SECURITY.md.

License

ai-registry is licensed under the Apache License 2.0.