OpenClaw

render-env-guard

Preflight-check Render service environment variables before deploys; catches missing keys and placeholder/template values that commonly break production rollouts.

daniellummis0 来源安装数☆ 0 仓库 Starsv1.0.0

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install daniellummis/render-env-guard

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Render Env Guard

Use this skill when a deployment is failing because environment variables are missing, placeholder values leaked from templates, or service selection is ambiguous.

What this skill does

Resolves a Render service by ID or name
Pulls service environment variables through Render API
Validates required keys exist and are non-empty
Flags suspicious values (template placeholders, localhost DB URLs, unexpanded ${VAR} refs)
Exits non-zero on any blocking issue so CI/deploy scripts can fail fast

When to use

Before render deploy / render blueprint updates
After onboarding a new environment
When runtime is showing config-related 5xx errors

Inputs

RENDER_API_KEY (required)
one of:
- RENDER_SERVICE_ID
- RENDER_SERVICE_NAME
optional:
- RENDER_API_BASE_URL (default https://api.render.com/v1)
- REQUIRED_ENV_KEYS (comma-separated, default: DATABASE_URL,DIRECT_URL,SHADOW_DATABASE_URL,NEXT_PUBLIC_APP_URL)

Run

bash scripts/check-render-env.sh

or with explicit values:

RENDER_SERVICE_NAME=my-service \
REQUIRED_ENV_KEYS="DATABASE_URL,NEXT_PUBLIC_APP_URL,STRIPE_SECRET_KEY" \
bash scripts/check-render-env.sh

Output contract

Prints a short report with PASS/FAIL
Returns exit code 0 when all required keys are valid
Returns exit code 1 when any key is missing/invalid or service lookup fails

Notes

This checker is intentionally strict to prevent bad deploys.
It validates values at the service level (what Render will inject at runtime), not local .env files.

来源信息

Source: github
Repository: openclaw/skills
Path: skills/daniellummis/render-env-guard
Version: 1.0.0
Commit: 54f971d34d42f3ec890afa1ecff5b11d51d75bed
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Render Env Guard

Use this skill when a deployment is failing because environment variables are missing, placeholder values leaked from templates, or service selection is ambiguous.

## What this skill does
- Resolves a Render service by ID or name
- Pulls service environment variables through Render API
- Validates required keys exist and are non-empty
- Flags suspicious values (template placeholders, localhost DB URLs, unexpanded `${VAR}` refs)
- Exits non-zero on any blocking issue so CI/deploy scripts can fail fast

## When to use
- Before `render deploy` / `render blueprint` updates
- After onboarding a new environment
- When runtime is showing config-related 5xx errors

## Inputs
- `RENDER_API_KEY` (required)
- one of:
  - `RENDER_SERVICE_ID`
  - `RENDER_SERVICE_NAME`
- optional:
  - `RENDER_API_BASE_URL` (default `https://api.render.com/v1`)
  - `REQUIRED_ENV_KEYS` (comma-separated, default: `DATABASE_URL,DIRECT_URL,SHADOW_DATABASE_URL,NEXT_PUBLIC_APP_URL`)

## Run

```bash
bash scripts/check-render-env.sh
```

or with explicit values:

```bash
RENDER_SERVICE_NAME=my-service \
REQUIRED_ENV_KEYS="DATABASE_URL,NEXT_PUBLIC_APP_URL,STRIPE_SECRET_KEY" \
bash scripts/check-render-env.sh
```

## Output contract
- Prints a short report with `PASS`/`FAIL`
- Returns exit code `0` when all required keys are valid
- Returns exit code `1` when any key is missing/invalid or service lookup fails

## Notes
- This checker is intentionally strict to prevent bad deploys.
- It validates values at the service level (what Render will inject at runtime), not local `.env` files.

搜索