A preflight-check utility for Render services that prevents deployment failures by validating environment variables and catching placeholder values.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install render-env-guard
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install render-env-guard using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Render Env Guard is a specialized developer tool designed to safeguard your production environment. As part of the Openclaw Skills ecosystem, it performs rigorous pre-deployment checks on your Render services to ensure that all critical environment variables are correctly configured. By proactively identifying missing keys, unexpanded variables, or suspicious template placeholders before a rollout begins, this skill eliminates common runtime errors and reduces the friction of cloud deployments.
This utility is specifically built for teams using Render who want to ensure that their runtime environment matches their expectations. It validates values at the service level—exactly what Render will inject at runtime—rather than just checking local files, providing a higher level of deployment confidence.
To integrate this into your workflow with other Openclaw Skills, ensure you have curl and python3 installed in your environment.
Set your Render API key and run the guard script:
export RENDER_API_KEY="your_api_key"
bash scripts/check-render-env.sh
For advanced configurations involving specific services and custom required keys:
RENDER_SERVICE_NAME=my-web-app \
REQUIRED_ENV_KEYS="DATABASE_URL,STRIPE_SECRET,REDIS_URL" \
bash scripts/check-render-env.sh
The skill interacts with the Render API and requires specific metadata to function.
| Input Variable | Requirement | Description |
|---|---|---|
| RENDER_API_KEY | Required | Your Render personal access token. |
| RENDER_SERVICE_NAME | Optional* | The name of the service to check (*one service identifier required). |
| RENDER_SERVICE_ID | Optional* | The unique Render ID (e.g., srv-xxx) for the service. |
| REQUIRED_ENV_KEYS | Optional | Comma-separated list of keys to validate (Default: DATABASE_URL, DIRECT_URL, etc.). |
| RENDER_API_BASE_URL | Optional | The API endpoint (defaults to https://api.render.com/v1). |
Loading
A pre-deployment utility that detects environment variable drift between local configurations and live Render services to prevent failed builds.

An automated utility to synchronize environment variable tables in your README with .env.example files to prevent documentation drift.

A pre-deployment health check tool for Prisma migrations that prevents broken database states in production.

Cluster noisy JUnit test failures into stable, repeatable fingerprints to streamline CI triage and identify root causes.

A developer tool for replaying signed Stripe webhook events to verify idempotency and simulate retry behaviors.

Automatically sync your active project phase and task checklist from PLAN.md to TASKS.md to ensure development alignment.








































