Skills Store (optional)

Overview

Agent OS can use an optional skill store (registry) to list and install skills by slug. The store is a separate service or app that exposes:

• A registry endpoint — Returns a list of skills (slug, name, description, version, url).
• Skill content — Each skill’s content (e.g. Markdown + tools) is fetched from the url in the registry.

Agent OS does not include a store app in this repo. You can:

• Run your own store (e.g. SulalaHub-style app) and point Agent OS at its registry URL, or
• Install skills only from local folders (~/.agent-os/skills/), system skills (seed dir), or upload (zip / Markdown).

Using a store from Agent OS

1. Configure the registry — In the dashboard (Settings) or via config, set the store’s registry URL (e.g. https://your-store.example.com/api/sulalahub/registry). The exact key may be in config or env (e.g. a store URL used by the dashboard and by POST /api/skills/install).
2. Browse and install — In the dashboard, open Skills and use “Add from registry” or “Install from store” to see the list and install by slug. Or call POST /api/skills/install with body { "slug": "weather" } (or similar as implemented).
3. Registry contract — The agent expects the registry to return something like:
   • GET <registry_url> → { "skills": [ { "slug", "name", "description", "version?", "url" } ] }.
   • Each skill’s url is used to fetch the skill content (e.g. Markdown or a zip). Paid skills may require ?license=TOKEN.

The in-repo API GET /api/skills/store-registry returns the current registry data (skills list, storeBase, registryUrl) if configured.

Adding skills without a store

• Copy — Copy a skill folder into ~/.agent-os/skills/<name>/ with skill.yaml (or SKILL.md) and optional tools.yaml.
• System skills — Put skills in the seed dir (e.g. data/skills/) and run Install system skills (dashboard or POST /api/skills/install-system).
• Upload — Use POST /api/skills/upload (zip) or POST /api/skills/upload-skill-md (Markdown) if the dashboard or API supports it.

Store roadmap (external)

If you run a SulalaHub-style store (separate repo/app), its roadmap (registry contract, storefront, submit, admin, paid skills, etc.) lives in that repo (e.g. store/ROADMAP.md). Agent OS only consumes the registry and installs from URLs; it does not implement the store itself.