iblai vibe plugin
Over 150 skills for building apps on the ibl.ai platform: sign-in, agent chat, profiles, analytics, desktop and mobile builds
- 229 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The connect skill writes the organization key and an API token into the project's env files
- The iblai-api-* skills manage users, roles, billing and organization data over REST
- The security folder holds reconnaissance and audit tools, to be used only with the system owner's permission
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/iblai-vibeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The connect skill writes the organization key and an API token into the project's env files
- The iblai-api-* skills manage users, roles, billing and organization data over REST
- The security folder holds reconnaissance and audit tools, to be used only with the system owner's permission
This is third-party code. Review the repository files before installing.
What it does
A set of skills for an app on the ibl.ai platform that your agent builds. The skills install into Claude Code, Codex, Cursor, OpenCode or Copilot with `npx skills add iblai/vibe --all`, and Claude Code users can take a plugin with the same set plus an SDK-docs MCP server. Work begins with the /iblai-vibe-start skill: it asks four questions (new project or existing, one organization, several or headless, who signs in, what the app is about) and writes the answers to iblai.env so later skills do not ask again. The skills come in two families. The iblai-vibe-* skills add ready components on Next.js: ibl.ai SSO sign-in, agent chat, profiles, account and organization settings, notifications, invitations, analytics and the agent settings tabs. The iblai-api-* skills do the same over REST, for a script, CI or your own backend. Separate folders cover billing and monetization, Open edX courses, testing, deployment and builds. The /iblai-vibe-connect skill ties the project to an ibl.ai organization in the browser. For desktop and mobile there is /iblai-vibe-ops-build (macOS, Windows, Linux, iOS, Android), and /iblai-vibe-ops-deploy returns the app's URL.
Who it is for. Teams and solo developers building an app with an agent, sign-in and an admin area on the ibl.ai platform who hand Claude Code or Codex the groundwork through ready-made skills.
Good fit when
- You need a new Next.js app with ibl.ai sign-in, agent chat and an admin area in one pass
- An existing app needs a profile, notifications or user invitations added through a separate skill
- A script or CI job must work with agents, the organization and analytics over REST: the iblai-api-* skills run without a UI
- The app must be built for macOS, Windows, iOS and Android, with all icon sizes made from one source image
- An existing codebase needs a production-readiness audit with the /iblai-vibe-deslop skill
Not a fit when
- The project has nothing to do with ibl.ai: the skills are tied to its platform, SSO and SDK
- You need a run entirely on your own servers without iblai.app: the platform code is licensed through the ibl.ai team
- You want a security check of someone else's service without the owner's permission: the eight skills in the security folder are meant for authorized testing
Example request
/iblai-vibe-start: I am building a new Next.js app with one organization, member sign-in and an agent chat, then connect the project to my organizationLimitations
- The set works against the hosted iblai.app environment. Running on your own servers needs a license to the platform codebase, issued by the ibl.ai team.
- The repository changes often and installed skills stay a copy. Refresh them with a repeat install or the /iblai-vibe-ops-upgrade command in Claude Code.
- The --all flag installs every skill at once, and the set has over 150.
- An ibl.ai account and organization must exist beforehand, with signup at ibl.ai/join.
How to disable. Delete the iblai-* folders from the agent's skills directory. In Claude Code, disable the plugin in the plugin manager. Remove iblai.env and the keys in the project's env files by hand, and revoke the issued API token in your ibl.ai organization.
FAQ
How do I install iblai/vibe in Claude Code?
Run `/plugin marketplace add iblai/vibe`, then `/plugin install iblai-vibe@iblai`: the plugin brings the same skills and an SDK-docs MCP server. Without the plugin, `npx skills add iblai/vibe --all` installs the skills.
How do iblai-vibe-* skills differ from iblai-api-*?
The first add visual components to the app: sign-in, chat, profiles, analytics. The second do the same over REST with no UI, for a script, CI or your own backend.
What lands in the project when it connects to an organization?
The /iblai-vibe-connect skill opens a browser and writes the organization key and a minted API token into the project's env files, and the token never enters the chat.
Can I run the platform myself?
The set targets the hosted iblai.app. Local or self-hosted deployment needs a license to the platform codebase, requested from the ibl.ai team.
Which agents does iblai/vibe support?
Claude Code, OpenAI Codex, Cursor, OpenCode and Copilot through `npx skills add`. The plugin with the SDK-docs MCP server is for Claude Code.
Discussion
No questions or reviews yet.
Related
PluginsA vibe coding workflow with skills: idea research, PRD, tech design, AGENTS.md, build, verification and debugging
VibeWise turns coding with an agent into learning: it asks for your approach first, you make the design decisions, and the agent writes the code
A skill for building on VibeCode Bitrix24: docs routing, keys and auth, Black Hole deployment and common mistakes
A skill and CLI that draw architecture diagrams from Prisma, OpenAPI, GraphQL and code, and check the docs in CI for drift from the code
Vercel AI SDK skill: an agent writes chat, streaming and agents from the docs of the installed package version
A plugin of 24 Claude Code skills for AI apps on Next.js, AI SDK 7, shadcn/ui and pgvector, with in-browser UI checks
README in short
The README gives three steps: install the skills, begin with /iblai-vibe-start, ship the app. It then lists what the ready starter app includes, six entities nearly every app touches and a table of skill folders. It also notes that installed skills stay a copy and need refreshing.