/iblai-vibe-agent

First time here? If iblai.env has no ARCHITECTURE=, run /iblai-vibe-start first (four questions; two minutes) — it decides single-org / multi-org / headless and who signs in, and every skill reads the answer.

Everything about configuring an agent lives behind one provider and one route layout. Set the provider up once (§1), then mount only the tabs your app needs (§2). Most apps need five or six; the rest are there when asked for.

Common setup (brand, conventions, env files, verification): see docs/skill-setup.md.

Prerequisites

• Auth in place (/iblai-vibe-auth, or vibe-starter).
• A real agent UUID — the last path segment of https://os.ibl.ai/platform/<org-key>/<agent-uuid>, or one created with /iblai-vibe-agent-create. Never invent one.
• The signed-in user must be the agent's owner, an org admin, or hold an editor role on it (/iblai-vibe-agent-access); otherwise tabs render "no access".

1. The provider (once)