← VibeRavenCONTENT HISTORY
WHAT CHANGED
added
Update to VibeRaven
Snapshot Oct 28, 2026 · 13:06 UTC · version 1.1.0
Package or technical metadata updated
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Save VibeRaven and check future changes in Following.
Up to 10 plugins free · no card required.
All fields and original values.
Is v2 template
Before
Oct 25, 2026 · 12:04 UTC
Not present
After
Oct 28, 2026 · 13:06 UTC
false
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
added /is_v2_template
BEFORE
Field was absent
AFTER
false
Full snapshot data
{
"canonical_app_id": "asdk_app_6abcde724e908191bfdaee83d7693940",
"connector_id": "asdk_app_6abcde724e908191bfdaee83d7693940",
"created_at": "2026-09-30T10:42:35.119976Z",
"discoverability": "LISTED",
"id": "plugin_asdk_app_6abcde724e908191bfdaee83d7693940",
"is_template": false,
"is_template_instance": false,
"is_v2_template": false,
"name": "viberaven",
"release": {
"app_ids": [
"asdk_app_6abcde724e908191bfdaee83d7693940"
],
"app_manifest": {
"apps": {
"viberaven": {
"id": "asdk_app_6abcde724e908191bfdaee83d7693940",
"required": true
}
}
},
"app_templates": [],
"description": "Read-only answers about VibeRaven, the repository check for AI-built apps that deploy on Vercel and use Supabase: what a finding means, the published launch guides, and a manual launch checklist per stack. The hosted server cannot see your repository; the check itself runs locally. It is advice, not a gate, and not a live database or security test.",
"display_name": "VibeRaven",
"id": "pluginrel_12fe1facf86c81919d6ae6330d373974",
"interface": {
"brand_color": "#B8860B",
"capabilities": [
"Explain a VibeRaven finding with source links",
"Search the published Vercel and Supabase launch guides",
"Give a manual launch checklist for a Supabase app before launch"
],
"category": "Developer Tools",
"composer_icon_dark_url": null,
"composer_icon_url": "https://files.openai.com/content?id=file_0000000036188243ba7ceedcb38c304c",
"default_prompt": "My VibeRaven report says rls_disabled. What does it mean and how do I fix it?",
"default_prompts": [
"My VibeRaven report says rls_disabled. What does it mean and how do I fix it?",
"Give me a launch checklist for my Lovable + Supabase app.",
"How do I find Supabase tables missing RLS in my migrations?"
],
"developer_name": "Ohad Krispin",
"logo_url": "https://files.openai.com/content?id=file_00000000a4188243825b0eee7b897c9f",
"logo_url_dark": null,
"long_description": "VibeRaven is a repository check for AI-built apps that deploy on Vercel and use Supabase. This plugin answers questions about it from the pages published on viberaven.dev.\n\nWhat it does:\n1. Explains a VibeRaven finding id, such as rls_disabled or env_var_drift: what the rule detects in repository files, why it matters, how to fix it and what it does not check, each part quoted with a link to its source page.\n2. Searches the published launch guides (Supabase RLS, env vars on Vercel, Stripe webhooks after deploy, OAuth and CORS errors after deploy, client handoff) and returns the title, link and short answer of each match.\n3. Returns the manual launch checklist for a Supabase app made with an app builder, or a Next.js + Supabase app on Vercel, with the official sources each page cites and one optional local VibeRaven step.\n\nWho it is for: people shipping a Vercel and Supabase app that was built with a coding agent or an app builder, before a launch or a client handoff.\n\nLimits: the hosted server cannot see your repository, database, dashboards or Vercel project, and it does not browse the web. The check itself runs on your machine with the npx command it names. VibeRaven is advice, not a gate, and a repository check, not a live database or security test. Nothing here is for other stacks or general SQL questions. No sign-in, and the server stores nothing you send.",
"plugin_category_id": "developer tools",
"privacy_policy_url": "https://viberaven.dev/privacy",
"screenshot_urls": [],
"short_description": "Launch checklists and findings",
"terms_of_service_url": "https://viberaven.dev/terms",
"website_url": "https://viberaven.dev"
},
"keywords": [
"launch-readiness",
"supabase",
"rls",
"vercel",
"checklist"
],
"mcp_servers": [
{
"key": "viberaven",
"metadata": {
"headers": {},
"type": "streamable-http",
"url": "https://viberaven.dev/mcp"
}
}
],
"onboarding_skill_name": null,
"requires_local_executor": false,
"skills": [
{
"description": "Use when the user has an AI-built app that deploys on Vercel and uses Supabase and asks whether it is ready to launch or hand off, wants to find Supabase migrations that create tables without row level security, or has a production error about RLS, env vars, the database connection, the service role key or a Stripe webhook. Runs the VibeRaven repository check where the host can run local commands, and says what to do instead where it cannot. Not for other stacks, general SQL or deployment questions, or a single local error.",
"interface": {
"brand_color": null,
"default_prompt": "Is my Vercel and Supabase app ready to launch? Run a VibeRaven check on this repo.",
"display_name": "Pre-launch check",
"icon_large_url": null,
"icon_small_url": null,
"iconography": "default",
"short_description": "Check a Vercel and Supabase repo"
},
"name": "prelaunch-check",
"plugin_release_skill_id": "pluginrsk_6abce75087048191a13fbf9f3366d2f3"
}
],
"version": "1.1.0"
},
"scope": "GLOBAL",
"share_url": "https://chatgpt.com/plugins/plugin_asdk_app_6abcde724e908191bfdaee83d7693940?open_in_app",
"status": "ENABLED"
}SHA-256 of public snapshot: ef5126e235bf9ade656df6eefc6cfefcac85e8c20c4d050c47b00e43e05d0fb6