The single entry point to building on ibl.ai. Every custom app on the platform needs the same dozen things — sign-in, an agent to talk to, users and admins, organizations, custom data, memory, analytics, billing — and each is a ready component plus a skill that wires it in. Read the table, open the skill, build. This skill builds nothing itself.
New to the platform? Read docs/platform-lifecycle.md first (join → your org → org key → API token → credits) — ten minutes. Words: docs/glossary.md.
What do you want to do?
Two families, one install. iblai-vibe-* (kind ui/ops/guide) mounts
a visual component in your app or ships it; iblai-api-* (kind api)
drives the same platform data headlessly — exact endpoints, curl, no screen.
★ = the six core families almost every app reads or writes — which scope stores
what: docs/catalogue.md#core. Full delineation:
docs/skill-kinds.md.
| You want… | With a screen (iblai-vibe-*) |
Headless (iblai-api-*) |
|---|---|---|
| To start, and you have not decided new/existing, one org or many, who signs in | /iblai-vibe-start — four questions, recorded in iblai.env, then routed |
same |
| A new app — sign-in, chat with an agent, users/admins, profile, admin area, custom data | /iblai-vibe-ops-init (copies vibe-starter; asks only for org key + token) |
— |
| Operate an org with no app — from a terminal, a script, CI, or your assistant | — | /iblai-api-login first, then the skill for the family below |
| Chat with an agent; customize the chat surface | /iblai-vibe-agent-chat (+ /iblai-vibe-agent-chat-sidebar, /iblai-vibe-project) |
iblai-api-agent-session, agent-chat |
| Find / browse agents | /iblai-vibe-agent-search |
iblai-api-search |
| ★ Create an agent; set its identity, visibility, capabilities | /iblai-vibe-agent-create → /iblai-vibe-agent-setting; all 24 tabs via /iblai-vibe-agent |
★ iblai-api-agent-setting, agent-create |
| ★ The user's profile (name, bio, image, education, résumé) | /iblai-vibe-profile |
★ iblai-api-profile |
| ★ Custom data per user — preferences, flags, onboarding progress, app state | /iblai-vibe-user-metadata |
★ iblai-api-profile-metadata |
| ★ Custom data per organization — settings, branding, toggles | /iblai-vibe-org-metadata, /iblai-vibe-account |
★ iblai-api-org |
| Users vs admins: directory, invites, roles, a User/Admin view | /iblai-vibe-admin, /iblai-vibe-invite, /iblai-vibe-rbac |
iblai-api-management, rbac, invite, scim |
| ★ Memory — what agents remember about people; agent knowledge | /iblai-vibe-memory-guide → /iblai-vibe-memory, /iblai-vibe-agent-memory |
★ iblai-api-agent-memory |
| ★ Analytics — usage, users, topics, transcripts, costs, audit, reports | /iblai-vibe-analytics, /iblai-vibe-agent-audit, /iblai-vibe-history |
★ iblai-api-analytics |
| Notifications (bell, inbox, alerts, admin send) | /iblai-vibe-notification |
iblai-api-notification |
| Money — how you are billed; charging your users | /iblai-vibe-pricing → /iblai-vibe-credit, -billing, -agent-billing, -monetization-app-paywall, -monetization |
iblai-api-billing, spend-caps |
| A navbar, an onboarding flow, a README | /iblai-vibe-navbar, /iblai-vibe-onboard, /iblai-vibe-readme |
— |
| Ship: a URL; macOS / Windows / iOS / Android; the stores | /iblai-vibe-ops-deploy, /iblai-vibe-ops-build, /iblai-vibe-ops-release, /iblai-vibe-windows-msix, /iblai-vibe-iconography |
iblai-api-infrastructure (self-host) |
| Test before showing work; upgrade | /iblai-vibe-ops-test, /iblai-vibe-ops-upgrade |
— |
| Courses, applications, CRM, workflows, local LLMs | /iblai-vibe-course-access, -course-create, -application, -crm-overview, -workflow, -local-llm |
iblai-api-catalog, apply, crm |
| Anything with no component | /iblai-vibe-api — server route + Api-Token inside the app |
the iblai-api-* skill for that family (51) |
Not sure? Run /iblai-vibe-ops-init — the starter already has the first
eight rows wired.
The repo map
| Repo | What it holds | Get it |
|---|---|---|
iblai/vibe (this repo) |
Both families: iblai-vibe-* for building frontend apps (vibe-starter, SSO, chat, admin, metadata, memory, analytics, billing, deploy/build/release) and iblai-api-* for operating every platform REST family headlessly (formerly iblai/api), plus the hosted chat MCP server (mcp/) and tutorials/ |
npx skills add iblai/vibe --all |
iblai/os |
The Agentic OS (os.ibl.ai) — the reference app built on this SDK, and your org's admin console until your app has one | clone / browse |
iblai/vibe-agent |
A finished one-agent app with its own Stripe paywall — the model for "one creator, one agent, one price" | clone |
iblai/vibe-marketing |
43 marketing skills + platform CLIs | npx skills add iblai/vibe-marketing |
Keep the skills current
Installed skills are a copy. Re-run npx skills add iblai/vibe --all (or
/iblai-vibe-ops-upgrade) when your .claude/skills/iblai-vibe/SKILL.md is
older than two weeks or older than the
latest release.
Key links
- CLAUDE.md — agent guidance, the tiered skill catalogue
- docs/platform-lifecycle.md — join → org → credentials → credits → ship
- docs/security-model.md — where each credential lives and why
- docs/auth-model.md — sign-in, organizations, single-org / multi-org / headless · docs/domain-model.md — users, agents, organizations
- docs/skill-kinds.md — the two families and five kinds · docs/api-skills.md — the headless contract
- BRAND.md — brand guidelines
- ibl.ai/docs — every screen of the OS, documented