Installable SKILL.md bundles for Claude Code, Codex and Cursor. Your agent loads one when a task needs it: selling a plan, wiring sign-in, sending email, forming the company.
Personal skills, every project. For one project use .claude/skills.
User skills, every repository. For one repository use .agents/skills at its root.
This project. For every project use ~/.cursor/skills.
All seven skills, one line:
mkdir-p ~/.claude/skills && for s in vibiz vibiz-ai vibiz-analytics vibiz-auth vibiz-broadcasts vibiz-company vibiz-connectors vibiz-database vibiz-deploy vibiz-design vibiz-email vibiz-files vibiz-payments vibiz-social vibiz-use-one vibiz-web-data; do curl-fsSL https://app.vibiz.app/skills/$s.tar.gz | tar-xz-C ~/.claude/skills; done
mkdir-p ~/.agents/skills && for s in vibiz vibiz-ai vibiz-analytics vibiz-auth vibiz-broadcasts vibiz-company vibiz-connectors vibiz-database vibiz-deploy vibiz-design vibiz-email vibiz-files vibiz-payments vibiz-social vibiz-use-one vibiz-web-data; do curl-fsSL https://app.vibiz.app/skills/$s.tar.gz | tar-xz-C ~/.agents/skills; done
mkdir-p .cursor/skills && for s in vibiz vibiz-ai vibiz-analytics vibiz-auth vibiz-broadcasts vibiz-company vibiz-connectors vibiz-database vibiz-deploy vibiz-design vibiz-email vibiz-files vibiz-payments vibiz-social vibiz-use-one vibiz-web-data; do curl-fsSL https://app.vibiz.app/skills/$s.tar.gz | tar-xz-C .cursor/skills; done
~/.claude/skills
$ tree vibiz-payments
vibiz-payments
├── SKILL.md
└── references
├── payments.md
├── guide-payments.md
├── guide-app-payments.md
├── guide-webhooks.md
└── errors.md
$ head -4 vibiz-payments/SKILL.md
---name: vibiz-payments
description: Sell with Vibiz Stack payments - take money with no identity check and no Stripe account (Vibiz is the merchant; KYC only when the owner withdraws) or through the owner's own Stripe account, create a plan, add a checkout or Upgrade button, wire and verify payment webhooks, check subscriptions, and answer questions about fees (2% Vibiz fee plus card processing), the 7-day hold, refunds and withdrawing. Use when a Vibiz project (a vibiz.json in the folder, or the vibiz MCP tools) needs to take money or someone asks what a payment leaves them.
---
The skills
Seven skills, one per product.
Each install line downloads a .tar.gz that unpacks to <name>/SKILL.md and <name>/references/. The files are linked under each skill if you'd rather read them first.
vibiz
7 files
Start here for Vibiz Stack - what it can do (hosting, Postgres, sign-in, email and a business inbox, newsletters, AI models, files, payments, analytics with session replay, web data and design, social, connectors, company formation, domains), which skill covers each, how to log in or connect the MCP server, the one-key model (VIBIZ_APP_KEY), credits and spend limits, and the rules every Vibiz task follows (console links, owner-only steps). Use when starting with Vibiz Stack, when someone asks what Vibiz can do or which service fits, or when no other vibiz-* skill matches.
Use AI models through Vibiz Stack - chat with GPT, Claude, Gemini, Kimi, DeepSeek and every major lab's models by id, generate images (Nano Banana, GPT Image), text to speech and transcription, from an agent (MCP tools, CLI) or from an app with one key (OpenAI-compatible, new OpenAI(vibiz.ai)) - with per-call prices, the daily spend ceiling, project budgets and the account's own Google key. Use when an app needs an LLM, images or voice, when you need to generate an image or audio for a project, or someone asks what a model costs or which models they can call.
Set up and read a Vibiz Stack project's visitor analytics (cookieless pageviews, sources, countries, devices, custom and server-side events) together with session replay (masked recordings of what went wrong for visitors - JS errors, rage and dead clicks, abandoned forms - with insights and private links to watch a session), on Vibiz hosting or any other site. Use when someone wants analytics, to track visits or events, asks how their site is doing, where visitors come from, or what is going wrong for users - and always set up replays along with analytics.
Set up and change sign-in for a Vibiz Stack project - email and password, verification, magic links, Google, GitHub or Vercel sign-in, allowed email domains, and the callback URLs to register. Use when a Vibiz project's users need to sign in or its sign-in settings need changing.
Email a Vibiz Stack project's users and subscribers - contacts from the app at signup, safe CSV imports, newsletters and announcements (broadcasts) with a review step, and automations such as onboarding sequences and trial reminders - with one-click unsubscribe, sending pace and spam protection built in. Use when a business wants to email its users about its software, send a newsletter or product update, or set up an onboarding or re-engagement sequence.
Form the US company behind a Vibiz Stack project (LLC or C-Corp, any state) - read the fee catalog in cents, quote the total, draft the filing and fix its problems, and hand the real submission to the owner. Use when someone asks what forming an LLC or corporation costs through Vibiz, or wants to incorporate the business behind their app.
Connect a Vibiz Stack project to any outside HTTP API (a CRM, a weather or shipping API, an internal service) as a custom connector - import its OpenAPI spec or write a short manifest, set its key per environment, and call it through Vibiz with approvals for risky operations. Use when a Vibiz app or agent needs a third-party API that Vibiz doesn't provide itself.
Work with a Vibiz Stack project's Postgres database - get the development DATABASE_URL, run migrations, inspect tables and run read-only queries, without ever touching production rows. Use when a Vibiz project needs schema changes, queries, seed data or a look at its data.
Create a Vibiz Stack project and deploy it - vibiz init, the development env for local work, deploy to <slug>.vibiz.app, previews, promote and instant rollback, run the app on another host with one key, or export it (code, database, env guide) to take it elsewhere. Use when an app should go live on Vibiz or a Vibiz project needs a new deployment or a rollback.
Make the UI you build look good from the first screen - learn a website's design system with Vibiz Stack (web.design - colors, type scale, radii, spacing, component styles, section layout, screenshots) and apply its Tailwind v4, shadcn/ui or CSS theme and brief; or, with no reference, follow a short default design checklist. Use when building or redesigning a page, an app's UI, a landing page or a dashboard, when the person names a site they like ("make it look like Linear"), or when they have an existing site or brand the new app should match.
Send email from a Vibiz Stack project's own address (<mailbox>@<slug>.vibiz.app) - add the email resource, send from the app with @vibiz/app or HTTP, and stay within 50 emails per project per day - run the business's own inbox (hello@theirdomain.com kept in Vibiz; read, reply and send as it, with received mail treated as untrusted) - or forward that address to the owner's own inbox. Use when a Vibiz project needs to send welcome, receipt or notification emails, or the business wants email at its own domain, or asks to check or answer its mail.
Store and find files in a Vibiz Stack project's Files (a drive per project with permanent links) - find an image, video or audio you or the app generated earlier, upload a logo or product photo and get its link, import a file from a URL, private files with signed links, and file uploads from the app with one key. Use when you need a file's permanent URL, want to reuse something generated before, or an app needs to store user uploads, avatars or downloads.
Sell with Vibiz Stack payments - take money with no identity check and no Stripe account (Vibiz is the merchant; KYC only when the owner withdraws) or through the owner's own Stripe account, create a plan, add a checkout or Upgrade button, wire and verify payment webhooks, check subscriptions, and answer questions about fees (2% Vibiz fee plus card processing), the 7-day hold, refunds and withdrawing. Use when a Vibiz project (a vibiz.json in the folder, or the vibiz MCP tools) needs to take money or someone asks what a payment leaves them.
Post and schedule to a Vibiz Stack project's own social accounts (Instagram, TikTok, LinkedIn, X, YouTube, Pinterest, Threads, Facebook, Bluesky…), read post analytics, and pause, resume, re-budget or boost ad campaigns, with the owner approving anything live. Use when someone wants to publish, schedule, connect a social or ad account, or check how posts and campaigns perform for the business behind their app.
Use just one Vibiz Stack service (sign-in, database, payments, email, AI, analytics, replay, files, web data, connectors, social, company) from an app NOT hosted on Vibiz - another host, a plain HTML site, a mobile app's backend, a cron job or a script - creating a project with only that resource, adding the app's domain as running elsewhere, and giving the app its one key. Use when someone wants one Vibiz feature without deploying on Vibiz, or the app already runs somewhere else.
Get data from the web with Vibiz Stack - scrape a page or crawl a whole site to markdown, search the web or the news, screenshot a page, pull competitor ads from the Facebook / Meta Ad Library, find businesses on Google Maps, read Google or Trustpilot reviews, Instagram and TikTok profiles and hashtag posts, product prices from any shop, and public LinkedIn company pages. Use when someone wants to scrape, crawl, search the web, research competitors or their ads, find leads or places, collect reviews, check product prices, or look at an Instagram/TikTok profile, and the vibiz CLI or MCP tools are available.
A folder with a SKILL.md: a name, a description that says when to use it, and instructions, plus reference pages. The agent reads only the description until a task matches, then loads the rest, so skills cost nothing until they are needed.
Skills or the MCP server?
Both. The MCP server gives the agent the tools (create a product, deploy, send an email). A skill gives it the workflow and the facts: the order of steps, the fees and the hold, what only the owner may do. Skills assume the vibiz MCP server is connected.
Where do the files go?
Claude Code reads ~/.claude/skills (or .claude/skills in a project). Codex reads ~/.agents/skills (or .agents/skills in a repository). Cursor reads .cursor/skills and ~/.cursor/skills, and also .agents/skills and .claude/skills. Each archive unpacks to one folder named after the skill.
Do I need to restart?
Usually not: Claude Code and Codex pick up new skills in the running session. If one does not appear, start a new session.
Are the references up to date?
They are the pages of these docs, generated from the same source on every build, so a skill never says something the docs do not. Reinstall to update.