connect

Automate Fireproof Connect deployment to exe.dev Studio with tokens and environment files.

134|5|Updated Dec 24, 2025

Search Tags:#SSH #deploy #cloud-sync #connect #studio #Fireproof #exe.dev

Ready to run

npx skills add https://github.com/popmechanic/vibes-cli --skill connect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: connect
Source: https://github.com/popmechanic/vibes-cli/tree/main/skills/connect
Command: npx skills add https://github.com/popmechanic/vibes-cli --skill connect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the deployment of Fireproof Connect to a dedicated Studio VM on exe.dev, enabling a ready-to-use cloud sync backend for all your Vibes apps.

Core Features & Use Cases

One-click deployment of a Studio VM on exe.dev with the Fireproof stack.
Automated configuration of environment variables, tokens, and access controls.
Local project onboarding by generating a .connect file with studio endpoints for quick app integration.

Quick Start

Invoke the Connect deployment workflow from your agent by providing your Studio codename and Clerk keys, then run the deployment to provision and configure the backend.

Frequently Asked Questions about connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy Fireproof Connect to exe.dev Studio?▼

Fireproof Connect deployment is automated by provisioning a dedicated Studio VM on exe.dev and configuring the Fireproof stack for cloud sync. It uses an automation script to provision resources and produce a local .connect file for app integration.

What do I need to set up cloud sync for Vibes apps?▼

You need an exe.dev account, SSH access, and Clerk keys to set up cloud sync for Vibes apps. The deployment workflow uses these to configure environment variables, generate access tokens, and output a .connect file with studio endpoints.

Can I configure multiple Vibes apps to use one Fireproof backend?▼

Yes, the deployment provisions a single ready-to-use cloud sync backend on a Studio VM and generates a .connect file containing studio endpoints. This file enables quick integration across multiple Vibes apps.

Does deploying a Studio VM on exe.dev require manual SSH configuration?▼

Deploying a Studio VM on exe.dev does not require manual SSH configuration beyond providing access. The automation script provisions the dedicated VM, configures the Fireproof stack, and handles environment variable and token generation automatically.

What is the .connect file generated during Fireproof stack deployment?▼

The .connect file generated during Fireproof stack deployment is a local configuration file containing studio endpoints. It is produced by the automation script to enable quick onboarding and integration of your local projects to the cloud sync backend.