sales-vibecom

name	sales-vibecom
description	VibeCom (vibecom.app) platform help — an AI validate→build→distribute workspace for vibe coders and indie founders that doesn't stop at a score: a free no-signup Roast idea validator, a 10-dimension VC-grade Startup Idea Scorecard with live web research, a PRD generator and go-to-market plan you paste into Cursor, then AI marketing agents (SEO, GEO, Competitor Radar, social scheduling) run by a Growth Autopilot MCP server that reads your codebase to draft X/LinkedIn/blog content. Use when interpreting a VibeCom idea score or Scorecard, generating a PRD or GTM plan, setting up the Growth Autopilot MCP server in Claude Code or Cursor, weighing free vs Pro vs Growth plans, fixing marketing agents that won't publish or draft off-brand content, or asking whether it has a REST API. Credit/plan-metered; no public REST API. Do NOT use for comparing idea validators or the validate-before-building method (use /sales-idea-validation).
argument-hint	[describe what you need help with in VibeCom]
license	MIT
version	1.0.0
tags	["sales","idea-validation","platform"]

VibeCom Platform Help

VibeCom (vibecom.app) is a validate → build → distribute workspace for vibe coders and indie founders. Its thesis is the "vibe coder's distribution problem": AI coding made building ~10× easier, so distribution is now the bottleneck. So it starts as a validator — a free no-signup Roast and a 10-dimension Startup Idea Scorecard (live web research) — bridges into building with a PRD generator and GTM strategy generator you paste into Cursor, then keeps going into AI marketing agents (Vibe Marketing, SEO Agent, GEO Agent, Competitor Radar, social scheduling) run by a Growth Autopilot MCP server that lives in your IDE and reads your codebase/commits to draft X/LinkedIn/blog content you approve before it ships. No public REST API — the MCP server is the automation surface.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer from the user's prompt:

1. Where are you? (a) a free Roast score or a Startup Idea Scorecard result and unsure what it means, (b) generating a PRD or GTM plan to build from, (c) running the marketing agents (SEO / GEO / Competitor Radar / social scheduling), (d) wiring the Growth Autopilot MCP server into Claude Code / Cursor, (e) weighing free vs Pro vs Growth, (f) asking whether it has a REST API / how to get data out.
2. What's the idea, in one sentence? (helps interpret the score, the Scorecard, and the PRD/GTM).
3. What evidence have you got so far — a hunch, customer interviews, an AI score, a landing page, a waitlist, or someone offered to pay?

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

Step 2 — Route or answer directly

VibeCom spans validation, build-handoff, and marketing. Much of the thinking is tool-agnostic — route it:

The user's real question	Route to
Should I trust this score? How do I actually validate? The evidence ladder, comparing validators	/sales-idea-validation
Build the smoke-test / fake-door landing page the real demand test runs on	/sales-funnel
Grow a pre-launch waitlist and capture signups	/sales-audience-growth
Run the ~10 customer interviews that produce real evidence	/sales-idea-validation
Reddit-based real-demand signal to cross-check the idea	/sales-trendseeker
Choosing/comparing a dedicated social scheduler for ongoing distribution	/sales-social-media-management

When routing, give the exact command: "This is a validation-method question — run: /sales-idea-validation {the user's original question}"

Answer directly only for VibeCom-specific mechanics (the Roast, the 10-dimension Scorecard, the PRD/GTM generators, the SEO/GEO/Competitor-Radar agents, social scheduling, the Growth Autopilot MCP server, plans).

Step 3 — VibeCom platform reference

Read references/platform-guide.md for the full reference — the Roast vs the Scorecard, the PRD & GTM generators, the marketing agents (SEO / GEO / Competitor Radar / social), what's API/MCP vs UI-only, pricing/plan gates, and the Growth Autopilot MCP server. Read references/vibecom-api-reference.md for the programmatic surface (MCP server + why there's no public REST API/webhooks).

Answer using only the relevant section — don't dump the whole guide.

Step 4 — Actionable guidance

• The Roast score and the Scorecard are AI opinions, not demand. The free Roast is a 30-second gut check (1–10 + three risks + a one-liner); the Scorecard is a deeper 10-dimension VC-grade pass with live web research (competitor analysis, TAM/SAM/SOM, pain-point mapping, trends). Both can be confidently wrong. Keep the structured parts — the named risks, the competitor map, the market sizing, the GTM channels — and take the go/no-go from a real behavior test (smoke test / pre-sale). Route that to /sales-funnel + /sales-audience-growth, and cross-check with /sales-trendseeker.
• The PRD and GTM plan are build-handoffs, not validated plans — verify their numbers. VibeCom's differentiator is that it continues past the score into a full PRD (problem statement, personas, features, out-of-scope, flows, architecture, success metrics — markdown export to paste into Cursor / Claude Code) and a prioritized GTM plan. Treat the market-size and competitor sections as AI estimates to verify against real sources, and remember a spec you can build from is still not proof anyone will pay.
• The Growth Autopilot MCP server is the automation surface — there is no public REST API or webhooks. It runs inside your IDE (Claude Code / Cursor), reads your codebase/commits/milestones for product context, and drafts native content for 10+ platforms (X, LinkedIn, blog). Connect it from your VibeCom dashboard following their setup instructions — use the exact MCP endpoint/command shown in VibeCom's own docs; don't guess it. For anything the MCP server doesn't expose, copy from the UI — don't design a pipeline around a REST API that doesn't exist.
• Nothing publishes without your approval — feed it context if drafts read off-brand. The whole flow is Collect → Generate → Approve → Publish; if the SEO/GEO/social agents produce generic or off-brand content, give the tool more product context and brand-voice material (it learns voice progressively) and review before you connect channels and auto-publish.
• Present all pricing as best-effort, and explain the free-tier ceiling. The Free plan is one capped onboarding run (1 product, 2 channels) — repeat automation needs a paid plan; Pro adds channels + a 5-competitor product-research report; Growth adds Competitor Radar (weekly), SEO/GEO recommendations + AI images, and more channels. Point to vibecom.app/pricing. The free Roast tool is separate — no signup, ~3 roasts/day.
• Distinguish VibeCom from the one-shot scorers. Its cluster edge is that it doesn't stop at a verdict — it bridges validation → building (PRD/GTM) → (the AI marketing agents via the MCP server), which is its answer to the vibe coder's distribution problem. When a user compares it to a fast/free validator, lead with that continue-past-the-PRD contrast, note the Roast needs no card, and point them to for the full validator comparison.

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research (2026-07) — VibeCom is a young indie tool and the AI-validator space churns fast; verify tiers, the dimension set, and the MCP setup at vibecom.app.

• A VibeCom score is not validated demand. The Roast and Scorecard are AI opinions that can be confidently wrong; follow any green light with a real-behavior test (smoke test / pre-sale).
• The Scorecard, PRD, and GTM numbers are AI estimates. Market sizing (TAM/SAM/SOM) and competitor data come from live web research but are still model output — verify the figures before you rely on them.
• Free is one capped onboarding run. Repeat automation runs (ongoing content/SEO/social) require Pro or Growth; the free tier is 1 product / 2 channels. Confirm current limits at vibecom.app/pricing.
• No public REST API or webhooks — MCP only. The automation surface is the Growth Autopilot MCP server (IDE-native, reads your codebase to draft content). Don't plan a REST integration; there isn't one, and don't invent the MCP endpoint — take it from VibeCom's docs.
• The Roast is a separate free front door. ~30 seconds, no signup, ~3/day; it's a gut check, not the deeper Scorecard (which needs the app and, for depth, a paid plan).
• Dimension count differs across their surfaces. The blog describes a 10-point scorecard while some marketing says "7 dimensions" — read the live app for the current set rather than quoting a fixed number.
• Auto-publish needs connected channels + approval. Agents draft; you approve; publishing only happens on channels you've connected. Off-brand drafts usually mean thin product context — feed it more.

Related skills

• /sales-idea-validation — the tool-agnostic validate-before-building method and the full idea-validator comparison (start here to decide whether to trust any score)
• /sales-funnel — build the smoke-test / fake-door landing page the real demand test runs on
• /sales-audience-growth — grow a pre-launch waitlist and capture signups once you're testing demand
• /sales-trendseeker — Reddit-based real-demand signal to cross-check VibeCom's verdict
• /sales-social-media-management — compare dedicated social schedulers for ongoing distribution once you're publishing
• /sales-leanspark — the other validation tool in this cluster whose automation surface is an OAuth MCP server, if you're comparing MCP surfaces
• /sales-juma — an AI marketing workspace with a callable MCP server, for comparing content/marketing automation surfaces
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: "VibeCom roasted my idea 8/10 — should I build it?"

User says: "The Roast gave my idea an 8 out of 10 and the Scorecard looks strong. Am I good to build?" Skill does: Reframes the score as a directional AI gut check that can be confidently wrong, not proof of demand. Keeps the useful structured parts (the named risks, the competitor map, TAM/SAM/SOM, the GTM channels) to sharpen the pitch, and prescribes the real test — a smoke-test landing page with a pre-set conversion threshold, then a pre-sale — routing the build to /sales-funnel and signups to /sales-audience-growth, and offering /sales-trendseeker as a second signal. Result: The founder earns a go/no-go from stranger behavior instead of betting weeks on a number.

Example 2: "Turn my validated idea into something I can build"

User says: "VibeCom validated my idea — now I want a PRD and a go-to-market plan to actually ship." Skill does: Explains the PRD generator (problem statement, personas, features, out-of-scope, flows, architecture, success metrics, markdown export to paste into Cursor / Claude Code) and the GTM plan (prioritized channels + positioning from the competitor research), while flagging that the market/competitor sections are AI estimates to verify and that a build-ready spec is still not validated demand — the go/no-go belongs to a real demand test. Result: The user gets a build-ready PRD + GTM they trust for structure but verify for numbers.

Example 3 (automation): "Can I run VibeCom's marketing agents from Cursor — is there an API?"

User says: "I want VibeCom drafting my launch content from inside Cursor. Does it have an API or webhooks?" Skill does: States there's no public REST API or webhooks — the programmatic surface is the Growth Autopilot MCP server, which runs in the IDE, reads your codebase/commits for product context, and drafts native content for 10+ platforms (X, LinkedIn, blog) that you approve before publishing. Tells the user to connect it from the VibeCom dashboard using the exact MCP endpoint/command in VibeCom's docs (don't guess it), and that repeat automation runs need a paid plan. Result: The user connects the MCP server in Cursor and drafts on-brand content grounded in the codebase instead of hunting for a REST endpoint.

Troubleshooting

The marketing agents draft generic or off-brand content

Symptom: Social/blog/SEO drafts read bland or don't sound like the product. Cause: VibeCom learns brand voice progressively and grounds content in the product context it has; with thin context (a bare product description, no codebase connected via the MCP server) it produces generic copy. Solution: Feed it more product context and brand-voice material, connect the Growth Autopilot MCP server so it reads real codebase/commit context, and always review in the Approve step before connecting channels and auto-publishing.

"I ran out of runs on the free plan"

Symptom: The free plan won't generate more after the initial setup. Cause: The Free tier is one capped onboarding run (1 product, 2 channels); repeat automation runs (ongoing content/SEO/social, weekly Competitor Radar, SEO/GEO + AI images) are gated to Pro / Growth. Solution: Confirm current limits at vibecom.app/pricing and upgrade only if you genuinely want ongoing distribution — the free Roast validator needs no card, and one-off validation doesn't require a paid plan.

"I set up Growth Autopilot but can't export my data / find a REST API"

Symptom: The MCP server drafts content but there's no bulk export or REST endpoint. Cause: VibeCom is UI + MCP only — the Growth Autopilot MCP server reads product context and drafts content, and there is no public REST API or webhooks. Solution: Use the MCP server for what it's for (grounding content in your codebase from Claude Code / Cursor) and copy anything else from the UI. Don't design a pipeline around a REST API that doesn't exist, and take the MCP endpoint/command from VibeCom's own docs rather than guessing it.