Store Configuration (optional)

Overview

Agent OS does not include a skill store app. It consumes a registry URL (if you set one) to list and install skills by slug. The store itself is a separate application (e.g. SulalaHub-style) that you may run or use.

Agent OS side

• In Settings (or config), set the registry URL to your store’s registry endpoint (e.g. https://your-store.example.com/api/sulalahub/registry). The dashboard and POST /api/skills/install use this to fetch the skill list and install by slug.
• No other “store config” is required in Agent OS. Skill content is fetched from the url field in each registry entry.

Store app (if you run one)

If you deploy a separate store app (e.g. from a store repo), configure it with its own env vars, for example:

• Base URL — e.g. NEXT_PUBLIC_STORE_URL so the registry returns correct skill URLs.
• Admin — e.g. ADMIN_SECRET to protect the admin panel.
• Auth / DB / Stripe — As required by that app (Clerk, Supabase, Stripe for paid skills, etc.).

See that app’s README and .env.example for full store configuration. Agent OS only needs the registry URL pointing at that store.