rainbond-env-sync

Syncs non-sensitive Rainbond environment overrides into local env files.

7|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/goodrain/rainskills --skill rainbond-env-sync-goodrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rainbond-env-sync
Source: https://github.com/goodrain/rainskills/tree/main/rainbond-env-sync
Command: npx skills add https://github.com/goodrain/rainskills --skill rainbond-env-sync-goodrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping local environment configuration files in sync with a deployed Rainbond application is tedious and error-prone, especially when you must avoid leaking secrets or copying runtime-generated connection values. This Skill queries the live Rainbond platform and writes only meaningful, non-sensitive environment deltas into local files. ## Core Features & Use Cases - Environment Delta Sync: Queries Rainbond runtime state and writes only non-sensitive overrides that differ from the project baseline into .rainbond/env.preview.json or .rainbond/env.prod.json. - Secret and Metadata Filtering: Automatically skips passwords, tokens, certificates, provider connection envs (like DB_HOST, REDIS_PASSWORD), and platform-generated values. - Drift Detection: Compares local files against live Rainbond MCP state and reports any drift, trusting the runtime as the source of truth. - Use Case: After deploying a fullstack app to a Rainbond preview environment, ask the agent to sync the preview configuration locally so future bootstrap and troubleshooting runs need fewer manual inputs. ## Quick Start Ask the agent to sync the preview environment configuration of the linked Rainbond project into the local env file.

Frequently Asked Questions about rainbond-env-sync

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

FAQPage Schema
How do I sync Rainbond environment variables to local files?

Ask the agent to sync the preview or production environment for your linked project. The skill queries live Rainbond runtime state, filters out secrets and runtime metadata, and writes non-sensitive overrides into `.rainbond/env.preview.json` or `.rainbond/env.prod.json`.

What is the difference between env sync and a runtime status check?

Env sync maintains local reference files capturing durable, non-sensitive configuration deltas for future runs. It does not verify application health, repair runtime issues, or produce a live status report; use a troubleshooter skill for those tasks.

Does env sync store passwords or secrets locally?

No. The skill explicitly skips passwords, tokens, certificates, private keys, and secret-related usernames. Secrets belong in a separate `.rainbond/secrets.<env>.json` layer that is never merged into env sync output.

Why are DB_HOST and similar variables skipped during sync?

Values like `DB_HOST`, `DB_PORT`, `REDIS_PASSWORD`, and `KAFKA_BROKERS` are classified as runtime connection metadata injected by the platform or dependencies. They are ephemeral and auto-generated, so they are always excluded even when they differ from the baseline.

Can I sync environments if my project is not linked to Rainbond?

No. The skill requires `.rainbond/local.json` with `metadata.status` set to `linked`. If the project is unlinked, the sync stops and instructs you to link the project first rather than guessing the application identity.

What happens when local env files disagree with Rainbond runtime state?

The skill trusts Rainbond MCP responses as the source of truth. It updates the env file based on filtered runtime values and explicitly reports the detected drift, such as mismatched app names or changed override keys.