---
name: vvibe
version: 1.0.0
description: VVibe is an operations console for AI coding agents. This skill teaches you how to connect to VVibe, install skills into yourself, dispatch tasks to a user's local agent, and deploy demos via InsForge.
homepage: https://vvibe.ai
---

# VVibe — Agent Setup Skill

You are an AI coding agent (Claude Code, Cursor, Codex, Cline, etc.) helping a user build, monitor, or extend their business through **VVibe**. This document is the canonical entry point — read it once, then proceed with the workflow that matches what the user asked for.

## What VVibe is, in one line

> The GUI for your Product Agent — a dashboard the user (a non-technical creator) uses to monitor and configure what their AI agent (you) does on their behalf.

The user is the **principal**. You are the **actor**. The dashboard is **observability**, not a click-driven CRUD console.

## Two ways you'll be connected to VVibe

### 1. Daemon path (primary)

The user has installed the `vvibe` daemon — a small Go binary that runs on their machine, holds a WebSocket to the VVibe relay, and accepts dispatched prompts. You (the agent) are spawned by the daemon when the user clicks "dispatch" in the dashboard or via the API.

When you're invoked this way, your environment already has:

- A working directory inside the user's `vvibe allow`-listed roots
- The skills the user has installed (each is a directory under their agent skill path)
- Permission to run shell commands, edit files, and commit (no extra auth needed)

Dispatch entry point: `POST https://vvibe.ai/api/devices/:deviceId/dispatch` (called by VVibe's web layer, not by you).

Reference: <https://vvibe.ai/llms.txt> lists all relevant API paths.

### 2. MCP path (secondary — for cloud agents)

The user is running you in the cloud (Claude.ai web, Cursor, etc.) and has connected you to VVibe via MCP over HTTP.

- MCP server: `https://mcp.vvibe.ai`
- Transport: HTTP
- Auth: Bearer token (the user pastes their VVibe access token into your client config)

Key MCP tools you'll see:

- `vibe_list_skills` — fetch the live skill catalog
- `vibe_report_skill_installed` — call this after you successfully `npx skills add` a skill, so the dashboard reflects the install
- `vibe_fetch_pending_tasks` — pull queued health-check / sync tasks the user assigned
- `vibe_report_health_check` — send back a structured health-check result

## Installing VVibe skills into yourself

All VVibe skills live in one public repo: <https://github.com/vvibe/vvibe-skills>

Install one or more in a single command:

```bash
npx skills add vvibe/vvibe-skills --skill <id1> <id2> --yes
```

The `--yes` flag bypasses the interactive agent-selection prompt; required because you're an agent, not a human.

After installing, **always** report back via MCP:

```
vibe_report_skill_installed({ skillId: "<id>" })
```

The dashboard reads this to show installation state and version drift.

### Skill catalog (live)

| ID | Install package | Category | What it does |
|---|---|---|---|
| `analytics` | `vvibe-analytics` | data | Connects Google Analytics to surface traffic, audience, and campaign data in the dashboard. Covers utm tracking at the traffic / session level (acquisition reports). For signup-time first-touch attribution per user, install the member skill alongside. Add to measure what content and promotions drive growth. Requires `appBaseUrl` to be set (via `vibe_update_brand` or dashboard Settings) before the skill can operate. |
| `member` | `vvibe-member` | ops | Manages subscriber and member accounts — listings, segmentation, activity history, admin queries — and now also captures first-touch attribution (utm_*, referrer) at signup so creators can see where each paying user originally came from. Add to know your audience, act on it, and attribute growth to specific traffic sources / partners. |
| `sentry` | `vvibe-sentry` | security | Runs a pre-deploy security audit on the creator's codebase by orchestrating gitleaks (secret leaks), osv-scanner + npm audit (dependency CVEs), semgrep (OWASP / JS / TS static analysis), and a small VVibe-integration layer. Normalises every finding into a CRITICAL / WARNING / INFO grade and reports the summary back to the dashboard via vibe_report_health_check. Add when the creator is about to ship and wants to know their codebase is safe. |
| `email` | `vvibe-email` | ops | Run follower-email invitation campaigns end-to-end — draft a campaign with subject + HTML body (vibe_create_campaign / vibe_update_campaign), dispatch via vibe_send_campaign, read post-send analytics — plus wire up where the email CTA redirects (VVibe-hosted waitlist, self-hosted /waitlist/[slug], or directly into the creator's existing register flow via inviteRedirectPath). Add to reach members outside the platform and drive re-engagement. |

The full machine-readable catalog (with versions and rich metadata) is at <https://vvibe.ai/llms.txt>.

## Common workflows

### A. User asks: "What can VVibe do?"

1. Read this skill (you're reading it now).
2. Call `vibe_list_skills` to see what's available.
3. Summarize back in the user's voice — they are non-technical. Don't dump the catalog raw; ask what they want to accomplish and recommend 1–2 skills.

### B. User asks: "Help me set up <feature>"

1. Identify which skill maps to <feature> (Payment for monetization, Member for sign-up, Email for transactional mail, Analytics for traffic, Sentry for errors).
2. Install that skill: `npx skills add vvibe/vvibe-skills --skill <id> --yes`
3. Report: `vibe_report_skill_installed`
4. Follow the skill's own `SKILL.md` for the next steps — each skill has its own workflow.

### C. User wants to deploy a VVibe official demo

Each official demo lives in its own GitHub repository — one repo per demo, marked as a GitHub Template Repository so end users can click "Use this template" rather than fork. The full catalog is at the `vvibe-demo` topic page: <https://github.com/topics/vvibe-demo>. Each demo has a `.vvibe-demo.yml` file at its root declaring:

- Which VVibe skills are pre-installed
- Which InsForge template the demo uses
- The demo's identity (name, displayName, description)

If you find a `.vvibe-demo.yml` in the working directory, treat the repo as an official demo and follow its `README.md` setup section verbatim. The README has been written specifically for end-user flow: `vvibe login` → InsForge signup → `npx @insforge/cli create` → deploy.

### D. User asks to dispatch a task to their local agent

This is a dashboard action, not an agent action. Tell the user to open <https://vvibe.ai/dashboard/devices> and use the dispatch console. Agents don't dispatch to other agents.

## Partner integrations

### InsForge (hosting)

VVibe official demos are deployed on **InsForge** — Postgres, auth, storage, edge functions in one platform.

- Referral signup: <https://insforge.dev/?utm_source=vvibe>
- Agent setup doc: <https://insforge.dev/skill.md>
- CLI: `npx @insforge/cli`

When a user is working on a VVibe official demo and asks "how do I deploy this?", route them to the InsForge CLI workflow in the demo's README (don't try to invent a deploy path).

## Hard rules

- **Never** commit secrets the user pastes into chat — VVibe access tokens, InsForge admin keys, Stripe secret keys. These all stay in `.env.local` or out of the repo entirely.
- **Never** push to the user's remote without their explicit OK. The dashboard treats unscheduled pushes as anomalies.
- **Always** report skill installs via `vibe_report_skill_installed`. Silent installs break the dashboard's source-of-truth for what you have.
- The user is non-technical. If you need to surface an HTTP status code, Stripe error, or stack trace — wrap it in plain language explaining what failed and what they should do next.

## Reference

- Site: <https://vvibe.ai>
- Dashboard: <https://vvibe.ai/dashboard>
- Skills catalog (machine-readable): <https://vvibe.ai/llms.txt>
- MCP endpoint discovery: <https://vvibe.ai/.well-known/mcp.json>
- Skills source: <https://github.com/vvibe/vvibe-skills>
- Official demos (GitHub topic index): <https://github.com/topics/vvibe-demo>
- InsForge partner: <https://insforge.dev/?utm_source=vvibe>