Skip to content

Ageri

A personal AI operating system. Self-hosted, always-on, multi-agent. Brings your AI from "a tab you open" to "an environment you live in."

What this site is for

Documentation for building, publishing, and using Ageri skills. If you're looking for the platform itself — the orchestrator, agents, web UI — start with github.com/ageri-platform/ageri. These docs assume you already have an Ageri install running.

Where to start

  • Build your first skill

    Scaffold a skill from a template, validate it, ship it. End-to-end in fifteen minutes.

    First skill walkthrough

  • Build with AI

    Don't know Python? Describe what you want to Claude / Cursor / GPT and let the model write it. The SDK contract is small and well-documented; non-coders ship skills this way every day.

    AI-assisted authoring

  • CLI reference

    Every ageri skill ... command — init, test, pack, install, publish, upload, more.

    CLI reference

  • SDK reference

    Contract surface — what SkillBase is, what Task carries, what OrchestratorContext exposes.

    SDK overview

  • Marketplace

    Trust levels, what local / community / verified / platform mean, and where the marketplace ToS sits.

    Trust levels

What makes Ageri skills different from chat plugins

Skills are first-class processes the orchestrator routes to. They aren't system prompts, they aren't fine-tunes, they aren't external API tool-calls in a single LLM turn. They are:

  • Real Python code with a class-level contract (SkillBase)
  • Sandboxed by trust level (local / community / verified / platform)
  • Permission-declared (memory scopes, tool access, both opt-in)
  • Shipped as .ags bundles (gzip-tar archives with a signed manifest)

The result: an Ageri install can quickly grow a long tail of small, focused skills — each authored by anyone, each running in their own sandbox, each safe to ignore until needed.

What this site covers

Section What's inside
Getting started Install, the first scaffold-to-publish flow
Authoring skills AI-assisted authoring, manifest format, permissions, recorder-driven authoring
CLI reference Every ageri skill ... command
SDK reference Core contract — SkillBase / Task / SkillResult / OrchestratorContext / SkillPermissions / MemoryWrite
Marketplace Trust levels, ToS placeholder

How this site is maintained

These docs live in github.com/ageri-platform/ageri-docs. All pages are plain Markdown under docs/ — PRs welcome. The SDK reference will switch to auto-generation from the SDK package's docstrings once ageri-sdk ships as a standalone PyPI distribution; until then the page is hand-curated to stay in sync with the source by inspection.

License

Documentation is MIT-licensed. Examples in code blocks can be lifted into your own projects without attribution friction.