ChronoAIProject/Ornn

<p align="center"> <a href="https://ornn.chrono-ai.fun"> <img src="ornn-web/public/hero-brand-dark.svg" alt="Ornn — agent-facing skill-lifecycle API" width="100%" /> </a> </p> <p> <a href="https://github.com/ChronoAIProject/Ornn/actions/workflows/ci.yml"><img src="https://github.com/ChronoAIProject/Ornn/actions/workflows/ci.yml/badge.svg" alt="CI" /></a> <a href="https://github.com/ChronoAIProject/Ornn/releases"><img src="https://img.shields.io/github/v/release/ChronoAIProject/Ornn" alt="Latest release" /></a> <a href="LICENSE"><img src="https://img.shields.io/github/license/ChronoAIProject/Ornn" alt="License" /></a> &nbsp;<strong>The skill lifecycle API for AI agents, not another marketplace.</strong> </p>

---

What is Ornn

Ornn is an agent-facing skill-lifecycle API. AI agents call Ornn directly — over HTTPS — to manage the full lifecycle of their skills:

search → pull → install → execute → audit → build → upload → share

Closest analog: npm registry + npm CLI, fused, model-agnostic. It works for Claude, GPT, Gemini, or any custom agent runtime. Not locked to a single model.

Why we built it

Modern AI agents do real work by composing skills — packaged prompts, scripts, and tools the agent invokes on demand. As soon as you build more than one agent, the same gaps show up:

• No shared registry. Skills live in private repos, gists, and one-off config files. There's no way for an agent to discover one it doesn't already know about.
• Model-locked alternatives. Anthropic Skills, OpenAI custom GPTs, and Gemini Gems each ship a registry — but only for their own runtime. Skills don't cross.
• No lifecycle. Versioning, sandboxed execution, security audit, publish — every team rebuilds these from scratch.

Ornn closes the gaps. One model-agnostic registry, one API surface, and a CLI (nyxid) every agent can drive end-to-end. The web UI at ornn.chrono-ai.fun is a thin admin layer for