Stats
Actions
Tags
From wizbi-tools
Guide for building AI agents and automations with WizBI. Use when the user wants to build a custom agent, set up automations, connect external MCP servers, create custom tools (plugins), or use WizBI Agent as an AI backend for their app.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wizbi-tools:wizbi-agentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
WizBI Agent is the AI backbone behind WizBI. It's a multi-channel agent (Web, WhatsApp, Telegram)
WizBI Agent is the AI backbone behind WizBI. It's a multi-channel agent (Web, WhatsApp, Telegram) powered by Gemini with access to all WizBI Tools. You can extend it, build on top of it, or connect it to your own stack.
Add your own tools to WizBI — they become available to you (or your users) alongside built-in tools.
Use the factory tool to create a new plugin dynamically:
"Create a tool that queries our CRM at https://api.mycompany.com/customers"
Or build a full plugin in the wizbi-ai-tools repo and deploy it.
Skills are reusable prompt workflows you can activate for your agent.
Use skills-manager tools:
create_skill — Define a new skill with a name, description, and promptactivate_skill — Add a skill to your active set (injected into system prompt)list_skills / search_skills — Browse available skillsshare_skill — Share a skill with other usersConnect any MCP server to WizBI — it becomes available as tools in your agent.
Use external-mcp-admin:
"Connect my company's internal MCP server at https://tools.mycompany.com/mcp"
Up to 10 external MCP servers per user. Servers are auto-discovered via /.well-known/mcp.
Run agent prompts on a schedule — daily reports, reminders, monitoring.
Use cron or scheduler tools:
"Every morning at 8am, check my calendar and send me a WhatsApp summary"
If you're a developer, you can use WizBI as your AI backend:
Authentication: Your users authenticate via OAuth 2.1 PKCE → wz_ token
GET https://tools.wizbi.ai/.well-known/oauth-authorization-server
POST https://tools.wizbi.ai/oauth/register
GET https://tools.wizbi.ai/oauth/authorize
POST https://tools.wizbi.ai/oauth/token → wz_ token
MCP connection:
GET/POST https://tools.wizbi.ai/mcp
Authorization: Bearer wz_<token>
Discover available tools:
GET https://tools.wizbi.ai/.well-known/wizbi-tools.json
WizBI uses a unified identity — the same user across all channels:
| Channel | How identified |
|---|---|
| Web / Claude | Firebase Auth UID (Google or email) |
| Auto-registered on first message, same UID | |
| Telegram | Linked via 6-digit code |
| Phone | Firebase Auth phone, auto-merges WhatsApp |
Once linked, all channels share the same tools, history, and preferences.
| Type | Format | Use case |
|---|---|---|
| User token | wz_xxx | Personal use — all your tools |
| Agent token | wz_xxx (isAgentToken=true) | Programmatic/service use |
| Scoped token | wz_xxx (allowedPlugins=[...]) | Limit to specific tools |
Create tokens at https://tools.wizbi.ai or via POST /api/tokens.
https://tools.wizbi.ai/mcphttps://tools.wizbi.ai/.well-known/wizbi-tools.jsonhttps://tools.wizbi.ai/.well-known/oauth-authorization-serverhttps://tools.wizbi.ai/.well-known/agent.jsonnpx claudepluginhub wizbi-ai/marketplace --plugin wizbi-toolsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.